Implement single sign-on (SSO)
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
In general, Web applications hosted in a container are independent of other Web applications, and each Web application is configured with its own security implementation. To simplify the security configuration for third-party Web applications and provide a single point of entry to users, OpenEdge Management provides an SSO process—sharing a session cache implementation—for all Web applications running in its Web server.
To share a session cache implementation, you can use the sample Web application
shipped with OpenEdge Management as a template. A custom session cache configuration
shares session login information with the third-party Web application. You can use this
configuration as an SSO solution for your third-party Web applications or provide your
own security implementation.
Note: OpenEdge Management login configuration
is available in the
web.xml file and the shiro.in file in the sample Web application template
that is shipped with OpenEdge Management.