Page Comparison

...

• <G-REG_HOME>/repository/deployment/server/jaggeryapps/store/config/store.json 
• <G-REG_HOME>/repository/deployment/server/jaggeryapps/storepublisher/config/publisher.json 

"authentication": {
"activeMethod": "sso",

...

1. Start the WSO2 IS server node, and log in to the Management Console using admin/admin credentials and the following URL: https://<IS_HOST>:<IS_PORT>/carbon/
2. Click Main, then click Add in the Service Providers menu.
   
3. Enter 'publisher' for the Service Provider Name and click Register.
   
4. Click Inbound Authentication Configuration, next click SAML2 Web SSO Configuration and then click Configure.
   
5. Enter the following details:
   
   • Issuer: Enter 'publisher' for this.
   • Assertion Consumer URLs: Enter the URL of the Publisher node (e.g., In this scenario, it is running in 192.168.10.5 server without a port offset.), and click Add.

   • Enable Response Signing: Check this option.

     Info
     Herein, import the public key of the certificate, which is specified as Certificate Alias that is used in IS to G-Reg Publisher and Store. Otherwise, you will get SSL verification errors when logging in. This is applicable when you use a different keystore other than the default wso2carbon.jkskeystore.)

   • Enable Single Logout: Check this option.
   
6. Click Register.

7. Repeat the above instructions to create another service provider called 'store'.

   Note
   Enter 'store' for Issuer and enter the URL of the Store node (e.g., In this scenario, it is 'https://192.168.10.6:9443/store/acs' as it is running in 192.168.10.6 server without a port offset.) for Assertion Consumer URL.

   

Step 4 - enabling SSO in WSO2 G-Reg Publisher

Follow the steps below to enable Single Sign-on in WSO2 G-Reg Publisher node.

1. Change the following configurations in the <G-REG_HOME>/repository/deployment/server/jaggeryapps/publisher/config/publisher.json file.

   Code Block
   language js
   "authentication": { "activeMethod": "sso", "methods": { "sso": { "attributes": { "issuer": "publisher", "identityProviderURL": "https://192.168.10.3:9443/samlsso", "responseSigningEnabled": "true", "acs": "https://192.168.10.5/publisher/acs", "identityAlias": "wso2carbon", "useTenantKey": false } },

2. Enter the URL of the WSO2 G-Reg Store node as the value of the storeUrl parameter in the <G-REG_HOME>/repository/deployment/server/jaggeryapps/publisher/config/publisher.json file. 

...

...

1. (E.g., "storeUrl": "https://192.168.10.6:9443/store")

Step 5 - enabling SSO in WSO2 G-Reg Store

Change the following configurations in the <G-REG_HOME>/repository/deployment/server/jaggeryapps/publisher/config/store.json file, to enable Single Sign-on in WSO2 G-Reg Store node.

"authentication": {  
     "activeMethod": "sso",  
     "methods": {  
       "sso": {  
         "attributes": {  
           "issuer": "store",  
           "identityProviderURL": "https://192.168.10.3:9443/samlsso",  
           "responseSigningEnabled": "true",  
           "acs": "https://192.168.10.6:9443/store/acs",  
           "identityAlias": "wso2carbon",  
           "useTenantKey": false  
         }  
       },  

Now, start all servers as you have completed enabling Single Sign-On in them. When you log in to the WSO2 G-Reg Publisher using the 'https://192.168.10.5:9443/publisher/' URL, the browser redirects you to the IDP (WSO2 Identity Server) as shown below.

Image Added