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:
On Windows:
Stop Ubisecure CustomerID
net stop wildfly |
Edit win32.config, example (login.smartplan.com -> login.newplan.com)
cd "C:\Program Files\Ubisecure\customerid\application" Example:
# Ubisecure SSO installation path # The public visible URL address of Ubisecure CustomerID without path # The local listen address of Ubisecure CustomerID if reverse proxy server is used ... #ldap.suffix=cn\=Ubilogin,@uas.url.host.dn@ |
Run setup
cd "C:\Program Files\Ubisecure\customerid\application" |
Edit widfly config
cd "C:\Program Files\wildfly-14.0.1.Final\standalone\configuration" Example:
|
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
C:\Program Files\Ubisecure\customerid\tools>"%JRE_HOME%\bin\keytool" -delete -keystore "%JRE_HOME%"\lib\security\cacerts -storepass changeit -alias wildfly-trusted C:\Program Files\Ubisecure\customerid\tools>del "C:\Program Files\wildfly-13.0.0.Final\standalone\configuration\keystore.pfx" C:\Program Files\Ubisecure\customerid\tools>cert.cmd You may choose to import the self-signed certificate to JRE's cacerts truststore. Do you want to import the self-signed server certificate to your cacerts truststore? |
b. If you have a CA signed certificate:
Edit standalone.xml, example: <ssl> |
If you use the same cert than with SSO, it was added to cacerts already. Otherwise, add it to cacerts, see SSO instructions above.
Create new SAML2 identity files
cd "C:\Program Files\Ubisecure\customerid\application\custom"
|
Optionally download SSO metadata (This must be done if SSO external address has been changed)
cd "C:\Program Files\Ubisecure\customerid\tools" cd "C:\Program Files\Ubisecure\customerid\tools"
|
Start Widlfy, verify logs
Upload the new SAML identities to Ubisecure configuration directory
If you have changed rest.username and/or rest.password in eidm2.properties, temporatily comment them out and restart wildfly cd "C:\Program Files\Ubisecure\customerid\tools" cd "C:\Program Files\Ubisecure\customerid\tools" |
Restart Widlfy, verify logs
Modify properties files
- eidm2.properties |
Restart Wildfly, verify logs, verify functionality
All OIDC and SAML integrations need a new metadata / configuration if the host name was changed |
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|