You can configure the API Manager for SAML SSO by following the instructions below.
Step 1 - Configuring the Carbon Console for SSO
This step is done in order to have SSO between the API Manager's and Identitiy Server's management consoles.
<API-M_HOME>/repository/conf/security/authenticators.xml file and give the configurations as shown below.
disabledattributes in the
ServiceProviderID: The issuer name of the service provider.
IdentityProviderSSOServiceURL: The URL of the IDP. In this example, it is the URL of the Identity Server.
A Service Provider (SP) is an entity that provides web services. A service provider relies on a trusted Identity Provider (IdP) for authentication and authorization. In this case, the Identity Server acts as the IdP and does the task of authenticating and authorizing the user of the service provider.
Service provider and Identity Provider usually communicate with each other about a subject. That subject should be identified through NAME-ID. It should be in some format so that it is easy for the other party to identify it based on the format. Possible values for NameIDPolicyFormat are as below.
- urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified [default]
We are using urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified which is the default NameIDPolicyFormat and it is totally depend on the entities implementing on your own wish. For more information on NameIdentifiers, refer section 8.3 of SAML Core.
Make sure the
<priority> element of the
SAML2SSOAuthenticator is less than that of the
BasicAuthenticator handler. See here for more information.
If there are many WSO2 products in your environment, you can configure SSO for the management consoles to gain one-time acces to all of them without repeated authentication. You can do this by changing the
SAML2SSOAuthenticator configuration in the
<PRODUCT_HOME>/repository/conf/security/authenticators.xml file as shown above.
Step 2 - Configuring Publisher/Store for SSO
To configure SSO for the API Publisher, open the
<API-M_HOME>/repository/deployment/server/jaggeryapps/publisher/site/conf/site.json file and give the configurations as shown below.
Note that following parameters should be matched with the Service Provider configurations of Identity Server that you are configuring.
|enabled||Set this value to true to enable SSO in the application.|
|identityProviderURL||https://localhost:9444/samlsso. Change the IP and port accordingly. This is the redirecting SSO URL in your running WSO2 IS server instance.|
|keyStoreName||The keystore of the running IDP. As you use a remote instance of WSO2 IS here, you can import the public certificate of the IS keystore to the APIM and then point to the APIM keystore. The default keystore of the APIM is |
|keyStorePassword||Password for the above keystore. The default keyStorePassword is |
By default, in the ssoConfiguration in site.json described above signRequests parameter decide whether to sign the AuthRequest or not. We have enabled it by setting the value true in default configuration so that, all the AuthRequests passing will be signed.
identityAlias parameter is set to
wso2carbon in the above example. You can configure an external server by importing the certificate of the IdP to APIM, and changing the
identityAlias parameter value according to the certificate. To configure an IDP initiated SSO, you have to include the following additional parameters in the
To configure SSO for the API Store, open the
<API-M_HOME>/repository/deployment/server/jaggeryapps/store/site/conf/site.json file and change the
ssoConfiguration section similarly. This allows users to gain access to the Store applications directly, if they are authenticated against the Publisher.
|The URL of the SAML 2.0 Identity Provider|
|SAML2.SPEntityId=API_PUBLISHER||A unique identifier for this SAML 2.0 Service Provider application|
SAML2.SPEntityId should be the value of issuer you specify under
ssoConfiguration in the
<API-M_HOME>/repository/deployment/server/jaggeryapps/store/site/conf/site.json, which uniquely identifies your SAML identity provider. Therefore, it differes between the Store and Publisher according to the issuer that you configure.
Step 3 - Configuring the API Store for SSO in passive mode
If the passive mode is disabled and Single Sign-On (SSO) is enabled, it redirects the user to the SSO login page. Therefore, as the WSO2 API Store allows anonymous access, passive mode is enabled by default, so that irrespective of whether SSO is enabled or not it directs the user to the API Store URL, and enables the SSO work flow only when the Sign In button is clicked.
To disable the passive mode, set the property named
passive to false in the
By enabling passive mode in SSO Configuration, WSO2 API Manager enables Passive Authentication on Single Sign On.
From the two fundamental authetication models which are active and passive, active authentication is based on WS-Trust protocol on which a relying party is resposible of issuing the security token associated with the user credentials. But in passive authentication which is based on SAML 2.0 and WS-Federation protocols, the relying party does not control the login logic and relies on the IdP to issue the credentials.
Step 4 - Configuring an Identity provider
- To configure WSO2 Identity Server as the IdP, see Configuring Identity Server as IdP for SSO.
- To configure an external IdP, see Configuring External IdP through Identity Server for SSO.