Follow the sections in this guide to set up OneLogin 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 OneLogin 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
Step 1: Configure a new Application
- Login to OneLogin as an administrator and click on Applications
- Click on the
Add Appbutton and search for
- Select the
OpenId Connect (OIDC)app
- Change the Display Name of the app to
Open Metadataand click
- Configure the login Url (
http(s)://<domain>/signin) and redirect URI (
http(s)://<domain>/callback) as shown below
- Configure the users in the organization that can access OpenMetadata app by clicking on the
- Click on "SSO" and select
None (PKCE)for Token Endpoint.
Step 2: Where to find the Credentials
- Go to "SSO" and copy the Client ID
- Copy the Issuer URL
Create Service Account (optional)
This step is optional if you configure the ingestion-bot with the JWT Token, you can follow the documentation of Enable JWT Tokens.
Create Secret Key
- Navigate to "SSO" settings of the application and click on
Show client secretto copy the secret key
After the applying these steps, you can update the configuration of your deployment:
Configure OneLogin SSO for your Docker Deployment.Bare Metal Security
Configure OneLogin SSO for your Bare Metal Deployment.Kubernetes Security
Configure OneLogin SSO for your Kubernetes Deployment.
After everything has been set up, you will need to configure your workflows if you are running them via the
metadata CLI or with any custom scheduler.
Note that OneLogin SSO is a layer on top of Custom OIDC.
When setting up the YAML config for the connector, update the
workflowConfig as follows: