Enabling cross launch for applications integrated with different Remedy SSO servers
As a Remedy Single Sign-On administrator, you can use the cross launch functionality to enable single sign-on experience between applications that do not share the same Remedy SSO server and are deployed in different domains. The target application in this case is integrated with a Remedy SSO server, and the source application either can be a part of some third-party solution or can be integrated with another Remedy SSO server. For more information about these deployment use cases, see Deployment scenarios.
Before you begin
Before you can enable cross launch for applications not integrated with the same Remedy SSO server, verify that the following prerequisites are met:
- If the source application is integrated with a Remedy SSO server, it must not be the same server as integrated with the target application.
- The source application must use an iframe to cross launch the target application.
- To cross launch a target application, the source application must be able to construct a URL in the following format:
The public certificate for Java Web Token (JWT) validation must be available to the target Remedy SSO server.
Remedy SSO does not provide a mechanism for generating a JWT along with private and public signing keypair.
To enable cross launch for applications that do not share the same Remedy SSO server
- Configure preauthentication for Remedy SSO which is integrated with the target application. For instructions, see Configuring preauthentication.
- (Optional) If the source application is integrated with a Remedy SSO, configure any authentication for the Remedy SSO. For information about how to do this, see Setting up end user authentication.
To verify the single sign-on experience for a cross-launched application
- Log in to the source application, and click the link to the target application.
The target application is displayed.
- If you encounter any errors, review Troubleshooting authentication issues.