edit

Integration Guide#

There are two technical entities in standard application integration transactions:

  1. The application (a.k.a "client" or "RP" / "SP"), and;
  2. The identity provider (a.k.a IDP or OP)

The integration guide below offers a list of pre-existing SAML & OAuth 2.0 client software projects developers can use to secure and integrate their applications ("clients") with an Authorization Server (AS), like the Gluu Server.

Note

Due to a wide range of variability in implementation quality, Gluu (the organization) only provides support for the following client software projects.

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 integrating server-side web applications with an IDP like Gluu:

  1. Web server filters and reverse proxies;
  2. Leveraging OAuth 2.0 directly in your application.

Option 1 offers easier devops. Option 2 enables a tighter integration with centralized security policies into your application.

Web Server Filters#

Web Server filters are a tried and true approach to achieving SSO 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.

Gluu supports the following SAML and OpenID Connect web server filters:

Client Software#

Client software performs some of the heavy lifting for developers around leveraging OAuth 2.0 in applications. Calling API’s directly enables “smarter” handling of authentication and authorization in applications. For example, transaction level security can be more easily implemented by calling OAuth 2.0 APIs directly. This approach will have a positive impact on usability and security.

Gluu supports the following software to secure and integrate server-side web applications:

  • oxd (commercial software)

Single Page Apps#

Single Page Applications (SPAs) can be seen as a mix between traditional Web SSO and API access: the application itself is loaded from a (possibly protected) regular website and the Javascript code starts calling APIs in another (or the same) domain(s). For this use case, the OpenID Connect spec points to using the “Implicit grant type” for passing token(s) to the SPA since that grant was specifically designed with the “in-browser client” in mind.

Gluu supports the following software to secure and integrate SPA’s:

Native Apps#

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.

Gluu supports the following software to secure and integrate native apps:

SaaS / Off-the-shelf Applications#

Integrating SaaS and off-the-shelf applications with your Gluu Server should be fairly straightforward. Presumably the app already supports SAML or OpenID Connect and provides documentation for configuring your IDP (Gluu Server) for SSO.

There is existing Gluu documentation for configuring SSO to popular applications like Google and Salesforce. If there is not an existing guide, perform a Goolge search for <SaaS Provider> SAML or <SaaS Provider> OpenID Connect. Follow the provider's instructions for configuring your IDP for SSO and test (and re-test!).

Note

If the target application does not already support SAML or OpenID Connect, our best advice is find a similar product or provider that does support one of these open web standards for single sign-on (SSO).