Over a million developers have joined DZone.

Security Patterns: Single Sign On across Web Applications and Web Services

Build APIs from SQL and NoSQL data sources in seconds. Read the Creating REST APIs white paper, brought to you in partnership with CA Technologies.

The requirement is to have single sign-on across different web applications; once the user is authenticated he should be able to access all the web applications with no further authentication (by himself). Also, the web applications need to access a set of back-end services with the logged-in user's access rights and the back-end services will authorize the user (end user) based on different claims, like role.


 1. User hits the link to the WebApp.

 
2. WebApp finds out user is not authenticated and redirects to the SAML2 IdP.

 
3. SAML2 Idp checks whether the user has an authenticated session - if not will prompt for credentials, once authenticated there ,user will be redirected back to WebApp with a SAML token, with the set of claims requested by the WebApp.

 
4. Now, the WebApp needs to access a back-end web service with the logged in user's access rights. WebApp passes the SAML token to the PEP based on WS-Trust and authenticates it self [WebApp] to the PEP via trusted-sub-system pattern.

 
5. PEP will call XACML PDP to authorize the user, based on the claims provided in the SAML token.

 
6. XACML PDP returns back the decision to the PEP.

 
7. If it's a 'Permit' - PEP will let the user access the back-end web service.

The Integration Zone is brought to you in partnership with CA Technologies.  Create app backends instantly with REST APIs and reactive logic using CA Live API Creator.

Topics:

Published at DZone with permission of Prabath Siriwardena , DZone MVB .

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}