Single Sign-On (SSO) Integration Guide#
The integration guide will help you understand how to achieve SSO with your Gluu Server across custom developed, open source, off-the-shelf, and SaaS web and mobile applications. The most important thing to understand is that there are a variety of SSO integration strategies available depending on the type of application in question.
The following page provides a number of integration strategies for the most common types of applications. This is not a totally exhaustive list of integration mechanisms and strategies. However, the mechanisms described below have been tested to work with the Gluu Server and are well understood by our support and development staff.
Server Side Web Apps#
Many applications are "server-side", meaning the web page displays content but most of the dynamic business logic resides on the web server. Two design patterns have emerged for securing server-side web applications: (1) use of web server filters and reverse proxies, and (2) leveraging OAuth2 directly in your application. Which approach to use depends on the trade-off between easier devops (option 1), and how deeply you want to integrate centralized security policies into your application (option 2).
Web Server Filters#
Web Server filters are a tried and true approach to achieving single sign-on with web applications. The web server filter enforces the presence of a token in a HTTP Request. If no token is present, the Web server may re-direct the person, or return a meaningful code or message to the application. Your devops team will love this approach–they can just manage the web server configuration files. It will be crystal clear to them what policies apply to what URLs.
We recommend the following SAML and OpenID Connect web server filters:
Client software performs some of the heavy lifting for developers around leveraging OAuth 2.0 directly in their applications. Calling the API’s directly will enable “smarter” applications. For example, transaction level security can be more easily implemented by calling the APIs directly. This can have a positive impact on usability. Giving developers more ability to leverage centralized policies also increases re-use of policies, and ultimately results in better security.
We recommend the following client software to implement OpenID Connect in server-side web applications:
Single Page Apps#
We recommend the following client software to implement OpenID Connect in SPA’s:
To integrate native apps with your Gluu Server, we recommend the AppAuth libraries for iOS , MacOS, and Android. AppAuth strives to directly map the requests and responses of those specifications, while following the idiomatic style of the implementation language. In addition to mapping the raw protocol flows, convenience methods are available to assist with common tasks like performing an action with fresh tokens.
Integrating SaaS applications with your Gluu Server is fairly straightforward. Presumably your target app already supports SAML or OpenID Connect and provides documentation for configuring your IDP (Gluu Server) for SSO.
In the integration guide there is documentation for configuring the Gluu Server for SSO to a few popular SaaS applications like Google and Salesforce. This list is not exhaustive. You can configure SSO to any SaaS application that supports SAML or OpenID Connect authentication at an external identity provider.
If there is not an existing guide in our documentation, simply perform a Goolge search for
<SaaS Provider> SAML or
<SaaS Provider> OpenID Connect. Follow the provider's instructions for configuring your IDP (Gluu Server) for SSO and test (and re-test!).
If the SaaS application in question does not already support SAML or OpenID Connect, our best advice is find a similar product or provider that does integrate with your standards-based security infrastructure.