Logging in to WSO2 Products via the Identity Server¶
When using multiple products of the WSO2 in a deployment, you need to log in to the management console of each and every product. This can be an overhead and a waste of time. Hence, it is useful to configure single sign-on for all the WSO2 products in the deployment and obtain access to all by providing credentials only once.
- WSO2 Identity Server (4.0.0 onwards)
- WSO2 Enterprise Service Bus (4.5.1 onwards)
- WSO2 API Manager (1.4.0 onwards)
By default, all WSO2 servers start in the HTTPS port 9443 and HTTP port 9763. Therefore, when you run multiple WSO2 servers you must change the default ports so that there would be no port conflicts. So you must do the following port allocations for this scenario:
- IS runs in https port 9443 (default)
- ESB runs in https port 9445 (offset = 2)
By default, WSO2 servers use basic authentication for authentication. However, in a Single-Sign-On (SSO) environment, you must use SAML-based authentication to authenticate users to WSO2 servers. The following needs to be done in order to enable SSO:
Before you begin
For single sign-on to work, you need to configure the WSO2 products to share a common user store. For more information on configuring this, see Configuring the Primary UserStore.
Configuring WSO2 Enterprise Service Bus¶
Configure the port and the authenticator of the WSO2 Enterprise Service Bus.
- Download the WSO2 ESB from
here and extract
it. This unzipped folder is referred to as
<ESB_HOME>in this topic.
- Open the
<ESB_HOME>/repository/conf/carbon.xmlfile and change the port offset to
- Enable the
ServiceProviderID. This ID is used by the Identity Server to identify the ESB's requests. Change this value to
When the cluster is hosted on the cloud or on a remote server, the
IdentityProviderSSOServiceURLtag must be changed in the
<IS_HOME>/repository/conf/deployment.tomlfile. This should point to the host URL of the load balancer of the cluster. This is done because the authentication is done by the WSO2 Identity Server cluster and the load balancer will decide where the authentication request is sent to.
From WSO2 Identity Server 5.0.0 onwards, there are different SAML endpoints for each tenant. If the service provider calls the identity provider's SAML endpoint URL as https://is.com:9443/samlsso?tenantDomain=foo.com or the issuer name is appended with @\<TenantDomain> like email@example.com, the SAML requests are directed to the foo.com tenant.
VerifySignatureWithUserDomainparameter is used to make the most recent products switch behaviour to expect SAML responses in the previous way. I.e., if this is set as
true, it means that the SAML response is verified with the tenant's key that the authenticated user belongs to. If it is set to
falseit means that the SAML response is verified with the tenant's key to which the SAML request is directed to. This can be set in the
[admin_console.authenticator.saml_sso_authenticator] VerifySignatureWithUserDomain= true
Configuring WSO2 Identity Server¶
- Download the WSO2 Identity Server from here.
- Extract the .zip file.
- Open a terminal and navigate to the
- Start the Identity Server using the wso2server.sh file in Unix or wso2server.bat file in Windows.
- Once the server is started, visit the following URL:
- Sign in to the WSO2 Identity Server. Enter your username and password to log on to the Management Console .
Navigate to the Main menu to access the Identity menu. Click Add under Service Providers.
Fill in the Service Provider Name and provide a brief Description of the service provider in the resulting screen. If the service provider configuration is used by tenants as well, you must select the SaaS Application checkbox.
By default, the SaaS Application checkbox is disabled, which means the web application is not shared among tenants so only users in the current tenant (the one you use to define the service provider) will be allowed to log into the web application. Alternatively, if you enabled the SaaS Application checkbox, that means this web application is shared among tenants so users from any tenant will be allowed to log into the web application. For example, if there are three tenants, namely TA, TB and TC and the service provider is registered and configured only in TA.
If the SaaS Application configuration is disabled, only users in TA are able to log into the web application.
If the SaaS Application configuration is enabled, all TA, TB, TC users are able to log into the web application.
Expand the SAML2 Web SSO Configuration under Inbound Authentication Configuration.
Click Configure . Fill in the form that appears.
Fill up this page with the following configurations.
Use the following values to register the WSO2 ESB:
Issuer : carbonServer2
Assertion Consumer URL : https://localhost:9445/acs
Use fully qualified username in the NameID
Enable Response Signing
Enable Assertion Signing
Enable Single Logout
Make a note of the following when you are using tenant configurations. This can be done in all the WSO2 Carbon servers.
If you need to sign the SAML response using an authenticated user's tenant keystore, please add the following configuration. (By default, the response is signed using the certificate that belongs to the tenant where the service provider is registered). This property must be added if the SAML authenticator version in the WSO2 Carbon products that you are using is 4.2.2 or higher (
enable_user_domain_crptoproperty available in the
<IS_HOME>/repository/conf/deployment.tomlfile as shown below.
[saml] enable_user_domain_crpto= true
The above configuration is an alternative to the
VerifySignatureWithUserDomainproperty in the
Under the Local & Outbound Authentication Configuration you can configure different authentication mechanisms you like to enforce. For example you can configure a authentication chain and enable Multi-factor authentication for WSO2 Products.
Click Register to save the values and register each service provider created.
Configuring WSO2 API Manager¶
For more information on configuring IS as the identity provider in WSO2 API Manager, see Configuring Identity Server as IDP for SSO.Top