Page tree
Skip to end of metadata
Go to start of metadata

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

    net stop wildfly
  2. Replace the old eidm.url with the new hostname in the file C:\Program Files\Ubisecure\customerid\application\win32.config
  3. Run setup

    cd C:\Program Files\Ubisecure\customerid\application
    setup.cmd
  4. Delete the SAML configuration files associated with the old hostname

    del "C:\Program Files\Ubisecure\customerid\application\custom\saml2\sp\identity.properties"
    del "C:\Program Files\Ubisecure\customerid\application\custom\saml2\ap\identity.properties"
  5. Generate a SAML configuration for the new hostname

    cd C:\Program Files\Ubisecure\customerid\tools
    init-eidm-sp.cmd
    init-eidm-ap.cmd
  6. Update the Tomcat configurations

    cd C:\Program Files\Ubisecure\customerid\application\config\tomcat
    update.cmd
  7. Update the new SAML configurations to the DB

    cd C:\Program Files\Ubisecure\customerid\tools
    init-eidm-db.cmd
    init-eidm-repository.cmd

Ubisecure CustomerID now uses the new hostname.


On Linux:

  1. Stop Ubisecure CustomerID

    /etc/init.d/customerid stop
  2. Replace the old eidm.url with the new hostname in the file /usr/local/ubisecure/customerid/application/unix.config
  3. Run setup

    cd /usr/local/ubisecure/customerid/application
    ./setup.sh
  4. Delete the SAML configuration files associated with the old hostname

    rm /usr/local/ubisecure/customerid/application/sp/identity.properties
    rm /usr/local/ubisecure/customerid/application/ap/identity.properties
  5. Generate a SAML configuration for the new hostname

    cd /usr/local/ubisecure/customerid/tools
    ./init-eidm-sp.sh
    ./init-eidm-ap.sh
  6. Update the Tomcat configurations

    cd /usr/local/ubisecure/customerid/config/tomcat
    ./update.sh
  7. Update the new SAML configurations to the DB 

    cd /usr/local/ubisecure/customerid/tools
    ./init-eidm-db.sh
    ./init-eidm-repository.sh

Ubisecure CustomerID now uses the new hostname.