SSO
Follow the sections in this guide to set up SSO.
Security requirements for your production environment:
- DELETE the admin default account shipped by OM in case you had Basic Authentication enabled before configuring the authentication with SSO.
- UPDATE the Private / Public keys used for the JWT Tokens. The keys we provide by default are aimed only for quickstart and testing purposes. They should NEVER be used in a production installation.
Create Server Credentials
- Go to the console of your preferred SSO provider
- Create an OIDC client application with implicit flow enabled to get a client ID.
Create Client ID and Secret Key
In a Public client configuration, only the Client ID is required. Client Secret should not be provided, as public clients cannot securely store sensitive credentials.
- Navigate to your preferred OIDC provider console and create an OIDC client application.
- Generate client ID and secret key in JSON format.
After applying these steps, you can update the configuration of your deployment:
Docker Security
Configure SSO for your Docker Deployment.
Bare Metal SecurityConfigure SSO for your Bare Metal Deployment.
Kubernetes SecurityConfigure SSO for your Kubernetes Deployment.
Configure Ingestion
Once your server security is set, it's time to review the ingestion configuration. Our bots support JWT tokens to authenticate to the server when sending requests.
Find more information on Enabling JWT Tokens and JWT Troubleshooting to ensure seamless authentication.