Schedule demo
Home

Enterprise Edition - Single Sign-On (SSO) (Deprecated)

Overview

Applications Manager's Enterprise Edition supports Single Sign-On (SSO) - a mechanism which offers a user unified access, i.e users do not have to actively enter their credentials more than once in order to access multiple independent installations (your Central Server and Probe Servers). Users gain access to all their Probe Servers with a single user authentication into the Central Server, eliminating further prompts when they switch applications during a particular session.

Benefits:

  • Security - Capability to implement consistent authentication and authorization guidelines across your enterprise.
  • Resource savings - Reducing time spent re-entering passwords for the same identity or profile and central access management.
  • User Experience - Ability to move between services and portals securely and seamlessly without password prompts.

Enabling Single Sign-On

You can enable Single Sign-On in your Applications Manager Enterprise setup as follows:

  • Download the appropriate cas war file based on the Applications Manager's version installed.

    Applications Manager VersionWAR File
    16430 and abovecas_8.war
    16410 to 16420cas_8.war
    15690 to 16400cas_8.war
    15530 to 15670cas_8.war
    14270 to 15510cas_8.war file located under <Applications Manager Home>\working\resources directory of Central server.
    Below 14270cas.war
  • Place the downloaded .war file in the webapps folder in the following path: <Applications Manager Home>\working\apache\tomcat\webapps in your Central Server.
  • Start Applications Manager and navigate to the Settings tab.
  • Open User Administration under Applications Manager Server Settings.
  • Navigate to the SSO tab.
  • Check the Enable SSO checkbox.
  • Restart Applications Manager. SSO is enabled.

Note:

  • Single Sign-on in Probe Servers will be enabled only after Applications Manager is restarted. Please take care to perform the restart after a few minutes to ensure that the SSO key from the Central server is synced with the Probe Servers.
  • The Central server should be running when the Probe Server starts for SSO to work.
  • Users created in the Central server will be synced to the Probe Server.
  • No user creation or modification can be performed on your Probe servers
  • In case of HTTP 400 (Bad Request) error faced while accessing the Probe server monitor from the Central server, try implementing the following steps:
    • Make sure that the Probe server hostname shown in Central server and the hostname specified for am.appmanager.hostname key in the AMServer.properties file (under <Applications Manager Home>/conf/ directory) of that Probe server should be the same. If not, update the correct hostname in the Central server's Edit Probe Server page and save it. Then stop the Probe server and update the same hostname for am.appmanager.hostname key in AMServer.properties file (under <Applications Manager Home>/conf/ directory) of that Probe server. Finally, save the changes and restart the Probe server.
    • Update the Probe server hostname to lowercase in the Central server's Edit Probe Server page and save it. Then stop the Probe server and update the same hostname to lowercase for am.appmanager.hostname key in AMServer.properties file (under <Applications Manager Home>/conf/ directory) of that Probe server. Finally, save the changes and restart the Probe server.

Loved by customers all over the world

"Standout Tool With Extensive Monitoring Capabilities"

★★★★★

It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.

Reviewer Role: Research and Development

carlos-rivero
"I like Applications Manager because it helps us to detect issues present in our servers and SQL databases."
Carlos Rivero

Tech Support Manager, Lexmark

Trusted by thousands of leading businesses globally