Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page describes the steps that need to be performed concerning Ubisecure CustomerID when the Ubisecure SSO product used by Ubisecure CustomerID is upgraded.

If you upgrade Ubisecure SSO, you need to copy the Ubisecure CustomerID SSO Adapter configuration files from the old Ubisecure SSO installation to the new one.

To copy the Ubisecure CustomerID SSO Adapter files from an old Ubisecure SSO installation to a new one in Windows:

  1. After upgrading the Ubisecure SSO (as instructed in page Upgrading SSO in Windows), prior to removing the temporary ubilogin-sso-old folder, go to the folder containing the old configuration files:

    cd /D "%PROGRAMFILES%\Ubisecure\ubilogin-sso-old\ubilogin\webapps\uas\WEB-INF\"
  2. Copy the existing configuration files to the new installation folder: 

    copy 
    attribute-prefix.index
    eidm2-authorizer.properties 
    
    to
    %PROGRAMFILES%\Ubisecure\ubilogin-sso\ubilogin\webapps\uas\WEB-INF\
  3. Define UBILOGIN_HOME environment variable for the Ubisecure SSO server so that it points to the Ubisecure SSO installation path: %PROGRAMFILES%\Ubisecure\ubilogin-sso\ubilogin 

    set UBILOGIN_HOME=%PROGRAMFILES%\Ubisecure\ubilogin-sso\ubilogin
  4. Transfer the cid-sso-adapter-package-x.x.x-windows.zip file to the Ubisecure SSO server and extract it for example under the following folder: %PROGRAMFILES%\Ubisecure
  5. Run the Ubisecure CustomerID SSO Adapter update script: 

    cd /D "%PROGRAMFILES%\Ubisecure\cid-sso-adapter"
    update.cmd

    The Ubisecure CustomerID SSO Adapter jar files will be integrated to the Ubisecure SSO installation.

  6. Remove older versions of duplicate jar files from Ubisecure SSO: %PROGRAMFILES%\Ubisecure\ubilogin-sso\ubilogin\webapps\uas\WEB-INF\lib
  7. Run update on Ubisecure SSO in order to finalize the installation of the Ubisecure CustomerID SSO Adapter. This can be done with the following command: 

    "%PROGRAMFILES%\Ubisecure\ubilogin-sso\ubilogin\config\tomcat\update.cmd"

    Ensure that the diagnostics log (uas3_diag.year-month-day.log, which is by default located at %PROGRAMFILES%\Ubisecure\ubilogin-sso\ubilogin\logs) contains the following rows (with the current time): 

    2016-09-02 13:57:49,021 init CustomerID Authorizer started
    2016-09-02 13:57:49,021 authz eidm.authorizer: CidAuthorizer init started.
    2016-09-02 13:57:49,209 init CustomerID SQL: customeriddb PostgreSQL x.x.x
    2016-09-02 13:57:49,224 authz eidm.authorizer: CidAuthorizer init done.
    2016-09-02 13:57:49,224 init eidm: com.ubisecure.customerid.authorizer.CidAuthorizer: started
  • No labels