Keycloak SSO

Follow the sections in this guide to set up Keycloak SSO.

  • You need an administrator account. If you don't have, see Creating the first administrator.
  • Go to the URL for the Admin Console. For example, for localhost, use this URL: http://localhost:8080/admin/
  • Enter the username and password you created.
  • The Keycloak use Realms as the primary form of organization, we can't use the realm "master" for new clients (apps), only for administration, so change for your specific realm or create a new.
  • In this example we are used an existing one called "Data-sec".
  • Click on Clients in the menu.
  • Click on Create button.
  • Enter the Client ID and Protocol as the image.
  • Click on Save button.
  • Change "Acess Type" value from "public" to "confidential".
  • Change "implicit flow" and "service accounts" to enabled.
  • At the bottom of the same settings page, change the configurations to the openmetadata address.
  • The image below shows different possibilities, such as running locally or with a custom domain.
  • Click on Save button.
  • Navigate to the Credentials tab.
  • You will find your Client Secret related to the Client id "open-metadata"
  • Navigate to the Service Account Roles tab.
  • You will find your service account id related to the Client id "open-metadata"

After the applying these steps, the users in your realm are able to login in the openmetadata, as a suggestion create a user called "admin-user". Now you can update the configuration of your 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 KeyCloak SSO is a layer on top of Custom OIDC.

When setting up the YAML config for the connector, update the workflowConfig as follows:

    hostPort: 'http://localhost:8585/api'
    authProvider: custom-oidc
      clientId: '{your_client_id}'
      secretKey: '{your_client_secret}'
      domain: '{your_domain}'

Still have questions?

You can take a look at our Q&A or reach out to us in Slack

Was this page helpful?

editSuggest edits