By: Seyed Sahil user 06 Aug 2020 at 9:05 p.m. CDT

3 Responses
Seyed Sahil gravatar
This is related to support ticket https://support.gluu.org/single-sign-on/8665/saml-configuration-issue/. Consider this ticket as a continuation of above Hello, Thanks for the quick response. But we still need some additional information. The first paragraph looks fine will have to try that once. **Our Requirement** Configure Gluu as a service provider and an external IDP for authentication. Means user should be redirected to a URL (resource) after successfully authenticated with the external IDP. The flow should start from Gluu as we configure Gluu as an SP. **Here is what we Did** Created a Passport provider and registered the details like the authentication entry point (the external IDP's SSO end point, public certificate, etc. As per the documentation we have to add the metadata data of the provider supplied by Gluu and the public certificate copied from /idp/shibboleth endpoint to the external IDP. So far we have done this and we hope that this this the configuration required. Now, say we need to access a sample url say www.example.com via Gluu server. (so first it will take us to external IDP for authentication and then redirect us to the given URL) Actually we are trying to configure this using the documentation and running into issue. So it would be really great if you provide some details on the config. Thanks Seyed

By Mohib Zico staff 11 Aug 2020 at 11:55 p.m. CDT

Mohib Zico gravatar
Hi, >> Actually we are trying to configure this using the documentation and running into issue. What issue?

By Seyed Sahil user 12 Aug 2020 at 5:09 a.m. CDT

Seyed Sahil gravatar
Thanks for the response, actually what we are tried was to configure Gluu as a service provider. > Now, say we need to access a sample url say www.example.com via Gluu server. (so first it will take us to external IDP for authentication and then redirect us to the given URL) But in another discussion we came to know that to use Gluu as a Service Provider we have to build a discovery service first. But still, this use case was not included in the documentation.

By Mohib Zico staff 12 Aug 2020 at 5:14 a.m. CDT

Mohib Zico gravatar
I can see couple of tickets on same problem created by same organization. Please note that: community support is mostly run by community and for community; so whenever community create tickets, we highly suggest them to create "one problem - one ticket" method. So, all can take the benefit from it. >> But still, this use case was not included in the documentation. Honestly speaking, this is pretty standard use case and passport has it's own discovery. If you want to cover some special use case, you should get VIP support.