If you're working in Tomcat, you'll find the endpoints in this subsection in the /path/to/tomcat/webapps/openam directory. For other web application containers, you may find the endpoints in a different openam subdirectory.
Debug.jsp
Supports debug logging by service. For more information, see the Administration Guide chapter on Debug Logging by Service.
encode.jsp
Enables access to a page that encodes text passwords. The algorithm is based on PBEWithMD5AndDES, password-based encryption (PBE) using the MD5 message-digest algorithm, configured with the data encryption standard (DES)
getServerInfo.jsp
Supports requests for server information. As getServerInfo.jsp is encoded in some .java files, you should retain getServerInfo.jsp in your deployment.
isAlive.jsp
Verifies the current status of the OpenAM service; the "Server is ALIVE:" message also verifies activity on OpenAM systems behind load balancers. This can be a useful tool in a production environment.
proxyidpfinder.jsp
Supports access to a remote identity provider, through the federation broker.
services.jsp
Lists active services within OpenAM. The details shown on this page can be used with the
ssoadm
command to create a second OpenAM server with matching services. Be aware, the
amadmin administrative user is hard-coded into this file. If you change the identity of the administrative user
to something other than amadmin, that user won't have access to services.jsp.
showServerConfig.jsp
Specifies configuration information for the system, including the URL, the OS, the Java VM, the configuration directory, and more.
ssoadm.jsp
Supports GUI-based access to the options associated with the ssoadm
command.
The ssoadm.jsp file is disabled by default. Instructions for enabling this feature are available from
the Administration Guide entry on OpenAM ssoadm.jsp.
validateWait.jsp
May be called by the validator.jsp or validatorMain.jsp files, to display progress in verifying the status of federation.
validator.jsp
Refers to the ValidateSAML2 function to identify the realm, IdP and SP for the federation.
validatorAuthFail.jsp
Starts an "Authentication Failed" message.
validatorFooter.jsp
Incorporates a "Back to Login" button in validatorMain.jsp.
validatorMain.jsp
Sets up a federation connectivity test. If you've set up a Federation Circle of Trust, this file is accessible from the "Test Federation Connectivity" option in the main OpenAM console.
validatorRpt.jsp
Opens a "Connectivity Test Results" window, specifying the status of a federation circle of trust. Tests relate to IdP authentication, SP authentication, account linking, single log out, single sign on, and account unlinking.
validatorStatus.jsp
Adds information to validator.jsp and validatorMain.jsp with federation status information as it relates to the currently configured circle of trust.
All of the validat*.jsp files near the end of this list relate to testing and verifying federation. It requires at least one identity provider (IDP) and one service provider (SP). At least one of these components must be configured remotely to set up a valid Circle of Trust (COT). If federation does not apply to your configuration, the validat*.jsp files are not essential to your configuration.