Reconfiguring the single sign-on after a System Manager upgrade

Last Updated : Feb 15, 2019 |
Prolog information
Metadata
Keywords:
Use this procedure to ensure that the single sign-on continues to work after a the System Manager upgrade.
With the single sign-on feature, you can access the System Manager and EPM using a single sign-on. After the System Manager upgrade, the single sign-on fails if:
  • Experience Portal files are not retained on the System Manager .
  • System Manager certificate is modified.
Before you begin
Verify whether you are able to access System Manager using the single sign-on feature from EPM.
  1. Log on to System Manager as a root user.
  2. Verify whether the experienceportalWelcome.html file exists at the following location: .
    ADDITIONAL INFORMATION:
    $JBOSS_HOME/server/avmgmt/deploy/ROOT.war/ experienceportalWelcome.html
  3. If the file does not exist, do the following:
    1. Navigate to the Readme.txt file located in the $AVAYA_HOME/Support/SMGR directory on the primary EPM.
    2. Copy the experienceportalWelcome.html file to System Manager.
  4. If System Manager has a new certificate after the upgrade, do the following:
    1. Import the new System Manager certificate to the EPM Trusted Certificates web pages by using the URL https://<SMGR FQDN>:443.
    2. Specify the certificate type as System Manager.
  5. Close all existing browsers and open a new browser to access System Manager using single sign-on.