Setting-up WSO2 Identity Server to connect to WSO2 GReg remotely

WSO Identity Server provides set of components that enable CardSpace authentication and OpenID which enables websites to provide strong authentication using information cards.


WSO2 registry now called as WSO2 GReg after its integration with governance solution handles the governance of web services while also behaving as a configuration management portal for services.


Even though Identity Server has its own H2 database, it can also be integrated with Greg to remotely connect and access GReg. The steps given below shows how the WSO2 Identity Server can be configured to access remote registry (GReg).

• As the first step download WSO2 IS and WSO2 GReg.

Something to note: By default all WSO2 products are set to start on 9443 and 9763 ports on https and http respectively.

So if we are going to use the same machine we need to change the ports of one of the products. I will do the required changes to WSO2 IS.

• Once downloaded unzip the files.

• Go to $WSO2_IS_HOME/conf and open axis2.xml. Change the http and https ports of the 'In Transports'.

• Now open transport.xml from the same location. Change http\https ports in it too.
  

• Open the identity.xml which is also in the same location. Change the ports to OpenID urls.

• Finally open the carbon.xml which also resides in the same location. Change the carbon.xml as below to access the remote registry.
  

- URL should be the url for registry.
- User name, password of the user credentials of the user who'll be allowed to manage remote registry for the Identity Server.
- Chroot can be any text which will be used to create a folder containing the resources related to IS.

• Now start WSO2 Greg first from the default ports 9443 and 9763.

• Start WSO2 IS after that from changed ports 9445 and 9765.

You're all set to work with WSO2 IS remotely accessing WSO2 Greg....! Now access https://localhost:9445/carbon to tryout the functionality.