Change the hostname of a CustomerID installation

Tested with CustomerID 5.3.5

During the initial testing of Ubisecure CustomerID, it is often needed to change a working system’s hostname. It can be done quite simply as described below.

Note: host name changes should never be done on a production system after it has gone live.

If the hostname of a Ubisecure CustomerID installation needs to be changed, it can be done following the steps below:

Step-by-step guide

On Windows:

1. Stop Ubisecure CustomerID

2. Edit win32.config, example (login.smartplan.com -> login.newplan.com)
   
   

3. Run setup

4. Edit widfly config

5. Certificate related changes
a.  If a self-signed TLS certificate is used, create a new self-signed certificate, add it to Java trusted certificate store

   b. If you have a CA signed certificate:

   If you use the same cert than with SSO, it was added to cacerts already. Otherwise, add it to cacerts, see SSO instructions above.

6. Create new SAML2 identity files

7. Optionally download SSO metadata (This must be done if SSO external address has been changed)

8. Start Widlfy, verify logs

9. Upload the new SAML identities to Ubisecure configuration directory

10. Restart Widlfy, verify logs

11. Modify properties files

12. Restart Wildfly, verify logs, verify functionality
    
    
    

Related articles