Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Information
This documentation supports the 25.3 and consecutive patch versions of BMC Helix Single Sign-On. To view an earlier version, select the version from the Product version menu.
Auth Proxy
Warning
Important
This section is hidden from customers, because this feature is available only to the BMC DevOps team.
The Auth Proxy server communicates with the BMC Helix Single Sign-On server and functions similarly to the BMC Helix SSO agent.
While deploying the Auth Proxy server, you don't need to integrate multiple applications with the BMC Helix SSO server and use the BMC Helix SSO agent. All you need is to have Auth Proxy installed and configured for communication with multiple applications.
While deploying Auth Proxy, you can enable single sign-on for any applications. For example, you can enable single sign-on for Jira, Remedy AR System, and BMC Helix Digital Workplace by setting up an Auth Proxy server to communicate with these applications by using individual ports.
Authentication flow for deploying Auth Proxy within the BMC Helix SSO server
In a browser, end users type an Auth Proxy URL that contains a host and a listening port. The listening port is mapped to the particular application in the Auth Proxy configuration.
Auth Proxy redirects the user's authentication request to the BMC Helix SSO server.
The BMC Helix SSO server checks the authentication type and sends the response to the Auth Proxy server.
The Auth Proxy server sends the authentication request to the client's browser.
Depending on the authentication type defined on the BMC Helix SSO server, the login page is either shown or not shown. For more information about these options, see Login and logout experience for end users.
The end user passes the BMC Helix SSO authentication.
Auth Proxy redirects the authenticated user to the application with the port specified in the Auth Proxy URL in step 1.
Success
Best practice To avoid double authentication, we recommend to turn off the default authentication on the application side.
