System Manager Settings page field descriptions

Last Updated : Jun 09, 2021 |
Prolog information
Metadata
Keywords:
Use the fields on this page to establish Single Sign-on with Avaya Aura® System Manager. For more information, see Configuring System Manager Single Sign-On.
Name
Description
Enable Single Sign-On
Allows you to enable or disable Single-Sign on. The options are:
  • Yes: The Single Sign-On is enabled.
  • No: The Single Sign-On is disabled.
    Note:
    1. When you click Save or Apply, Avaya Experience Portal verifies the System Manager settings only if the Enable Single Sign-On field is set to Yes. If all fields are valid, Experience Portal performs the following actions with System Manager that is configured on this page:
      • Register Experience Portal Resource Type, Experience Portal system roles, and Experience Portal Resource Instance.
      • Register navigation link.
      • Enable SSO client.
        If the Enable Single Sign-On field is set to No, Experience Portal saves the changes but does not verify the changes if there is no prior configured and enabled System Manager.
    2. When you have enabled Single Sign-On, the user can only modify the Navigation Link Display, User Name, and Password.
    3. If the user changes the Single Sign-In option from enabled to disabled, EPM tries to communicate with the previous configured System Manager to remove the SSO client and de-register the navigation link and Experience Portal Resource Instance. This is possible only if:
      • Experience Portal is able to access the previous configured System Manager.
      • System Manager User name and credentials configured are still valid.
    4. If Experience Portal cannot access System Manager, the page displays the Force Change check box. Use the check box to disable Single Sign-On with the configured System Manager.
Connection Settings section
Name
Description
System Manager FQDN
The fully qualified host name of the System Manager.
Note:
  1. The EPM server must match a part of the System Manager server’s domain name.
    For example, if the FQDN of System Manager server is smgr.us.avaya.com, the FQDN of EPM that can perform Single Sign-On with System Manager can be xx.us.avaya.com or xx.yy.avaya.com or xx.avaya.com.
  2. If the System Manager FQDN entered is different than the previous configured System Manager, you must restart EPM to enable Single Sign-On with the new System Manager.
Navigation Link Display
A link display that represents the primary EPM on the System Manager webpage. You can view this Navigation Link Display on the System Manager webpage from:
  • Home page Elements Experience Portal System.
  • Resource Instance when configuring a role.
Valid characters are number, letters, and any of "-", "(", ")", "/", "\", ".", "_", "{", "}".
Note:
If you have multiple EPMs that are enabled to perform Single Sign-On with the same System Manager, you must configure a unique Navigation Link Display.
User Name
A valid System Manager user who has the System Administrator role and is authorized to register Resource Type and Resource Instance with System Manager.
Note:
This user must be a System Manager user and not an EPM user. This System Manager user must be created from the User Management page in the Users tab in System Manager.
Password
The password of the System Manager user.
Note:
On the primary EPM, if you enable Single Sign-On with a System Manager and if you change the System Manager FQDN to a different System Manager, restart the primary EPM for Single Sign-On with the new System Manager to work properly.