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. 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. (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