SAML stands for Security Assertion Markup Language which is a XML based data format for exchanging authentication and authorization data between an identity provider and a service provider. The single most important requirement that SAML addresses is web browser single sign-on (SSO). Three main roles are defined in SAML Specification.
- The Principal: This is typically the user who tries to access a protected resource or service of a service provider.
- The Identity Provider: An Identity Provider (IdP) is responsible for authenticating users and issuing assertions which include authentication/authorization decisions and user attributes.
- The Service Provider: A Service Provider(SP) consumes the assertions issued by Identity Provider and provides services to the principals.
The main use case scenario covered by SAML is the Principal (the user) requesting access to resource or service from the Service Provider. Then the Service Provider, using SAML, communicates with the Identity Provider to obtain identity assertion. The Service Provider makes the access control decision, depending on this assertion.
SAML 2.0 is the latest version of SAML, which uses security tokens containing assertions to pass information about a user between an identity provider and a service provider.
SAML 2.0 provides five main specifications:
This article provides more information about above specifications.
SAML 2.0 web browser-based SSO profile
SAML 2.0 Web Browser based SSO profile is defined under the SAML 2.0 Profiles specification.
In a web browser based SSO system, the flow can be started by the user either by attempting to access a service at the service provider or by directly accessing the identity provider itself.
If the user accesses a service from a service provider:
- The service provider determines which identity provider to use (this is the case when there are multiple identity providers. SAML identity provider discovery profile may be used).
- The service provider generates a SAML message and then redirects the web browser to the identity provider along with the message.
- Identity provider authenticates the user.
- The identity provider generates a SAML message and then redirects the web browser back to the service provider.
- The service provider processes the SAML message and decides to grant or deny access to the user.
If the user accesses the identity provider directly, then only the steps 3, 4 and 5 are in the flow.
The message MUST contain an element which uniquely identifies the service provider who created the message. Optionally the message may contain elements such as Issuer, NameIDPolicy, etc. More information regarding the message can be found in SAML Core Specification.
The following diagram illustrates the scenario:
SAML 2.0 SSO assertion consumers
Service providers act as SAML assertion consumers. They have two basic functions:
- Create messages and redirect users to the identity provider with the created message.
- Process messages from the identity provider and make decisions based on them.
The following code is a sketch of a sample service provider servlet in a SAML 2.0 Web-Browser based SSO system.
When a web user attempts to access the above servlet, its doGet() method is called. Inside the doGet() method, it generates an message and then redirects the user to the Identity Provider.
After authentication is completed by the Identity Provider, it does a POST call back to the above servlet with a message. Then the doPost() method of the servlet gets called and inside the doPost() method, it retrieves the message from the request and then the message is passed to the SamlConsumer instance for processing.
To create an
<AuthnRequest> message using the OpenSAML library:
- Add the OpenSAML library to the build path of the project. You can download the open SAML JAR file from here.
- A sample <AuthnRequest> message can be found here.
According to SAML 2.0 specifications, the message must contain an element. Create the Issuer element first.
The message may contain many other elements like , etc. those elements can be created and added to the message in the same way.
Next encode the message.
Construct the redirection URL.
Redirect the user to the identity provider.
The Identity provider must use HTTP POST or artifact binding to transfer the
<SAMLResponse> message to the service provider. To read the
<Response> message issued by the WSO2 Identity Server, do the following:
- A sample <Response> message can be found here.
The response message must be fetched from the request.
The fetched “responseMessage” is unmarshaled and the SAML message is retrieved.
The retrieved SAML 2.0 Response message can be easily processed. For example, lets takes the User Name or the Subject's Name Id.
Alternatively, if the response is signed by the IdP, you can retrieve the certificate.
Likewise the message from the WSO2 Identity Server can be read easily.
Identity provider initiated SSO
To initiate IdP Initiated SSO you need to perform a HTTP GET/POST to the following URL (assume the registered service provider issuer ID is foo.com)
Note: To make this work, IdP initiated SSO should be enabled in your IdP.
This request will authenticate and redirect the user to the registered Assertion Consumer URL. Optionally, you can send in an 'acs' parameter as follows.
This request will authenticate and redirect the user to the URL in the 'acs' parameter itself.
Either you could have SP Initiated SSO only, or SP Initiated SSO and IdP Initiated SSO. You can't have IdP initiated SSO only. By design, SP Initiated SSO is more restrictive and secure. If a service provider is allowed to do IdP Initiated SSO, it would automatically imply that this service provider is allowed to do SP initiated SSO as well.