By default, users access the Advantage application by entering a valid User ID and Password on the Advantage Login page. If a site decides to access the Advantage application session using SSO via an identity provider portal and restrict normal login to the application then a System Administrator can control the information that is displayed on the Login page via the following parameters in the ADV30Params.ini file for the Advantage application:
HideLoginPage - This parameter controls what is displayed on the Login page. When this parameter is set to true, the following parameters determine what is displayed instead of the usual login fields:
HideLoginPageMessage - This parameter specifies the informational message that needs to be displayed on the Login page when the HideLoginPage parameter is set to true.
For example: “This application is currently down for maintenance.” or “Please navigate to the Login portal during this time.”
HideLoginAlternateURL - This parameter specifies the alternate login path or URL with a different port to access the Login portal instead of the normal Login page when the HideLoginPage parameter is set to true.
Note:
The delivered value for the HideLoginPage parameter in the ADV30Params.ini file is false. When set to false, the normal login fields are displayed.
This functionality is also applicable when the application is accessed via a mobile device.
When a user signs out of the application or is timed out of the Advantage application, the system redirects the user to a page where the user is allowed to sign back in using their user ID and password. However, for sites that utilize single sign-on, this is problematic as most users do not know their Advantage credentials because they do not use the Advantage login page. Therefore, the following parameters in the ADV30Params.ini file should be updated by sites that want to customize the logout page.
LogoutPage - When this parameter is set to false (the default value), the user is transitioned to the login page after logging out or after a session timeout. If a site does not want the user transitioned to the login page, this parameter should be set to true. The user is transitioned to a logout page, and the message displayed on this page is controlled by the value of the LogoutPageMessage parameter.
LogoutPageMessage - This parameter includes the custom text that your site wants displayed to the user on the logout page when the LogoutPage parameter is set to true. The value of this parameter should be updated if the LogoutPage parameter is set to true.
LogoutAlternateURL - This parameter includes the URL that the user is directed to when they select the Sign In Portal button on the logout page. For example, if a custom logout page is enabled and the user clicks on the Sign In Portal button, the system opens to a page using the URL specified in the new LogoutAlternateURL parameter instead.
Additionally, Advantage 4 provides the ability to configure information messages on the HideLoginpage for disabled and locked users when the Single Sign On configuration is in place. Using the given configurable text (CTEXT) message codes, the default messages can be updated at the site level from the Configurable Text (CTEXT) page.
For disabled user account:
Page Title - If a user trying to login has a disabled user account, then the page title displayed to this user is ‘Account Disabled’.
Message text - "Your account is disabled. Please contact the system administrator.".
This configurable message can be modified at the site level using the CTEXT message code - ACCDSBMG.
For locked user account:
Page Title - If a user trying to login has a locked user account, then the page title displayed to this user is ‘Account Locked’.
Message text - "Your account is locked. Please contact the system administrator.".
This configurable message can be modified at the site level using the CTEXT message code - ACCLCKMG.
Note: These page titles and system feedback messages only show when the HideLoginPage parameter is set as true in the ADV30Params.ini file. Application server restart is required after modification of CTEXT messages.