Pere Miquel Brull 6fcdf803e6
Prepare Docs V1 structure (#11089)
* Prepare Docs V1 structure

* Point to the v1.0.0 images dir

* Use the same ssh key

* Use new key

* Add connectors icons

* Update images
2023-04-17 16:45:47 +02:00

5.4 KiB

title slug
Auth0 SSO /deployment/security/auth0

Auth0 SSO

Follow the sections in this guide to set up Auth0 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 Auth0 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: Create the Account

  • If you don't have an account, Sign up to create one.
  • Select the Account Type, i.e., Company or Personal
  • Click I need advanced settings and click next.
create-account
  • Provide the Tenant Domain, select the region and click on Create Account.
create-account
  • Once done, you will land on the dashboard page.
create-account

Step 2: Create a New Application

  • Once you are on the Dashboard page, click on Applications > Applications available on the left-hand side panel.
create-app
  • Click on Create Application.
create-app
  • Enter the Application name.
  • Choose an application type and click on Create.
create-app

Step 3: Where to Find the Credentials

  • Navigate to the Settings tab.
  • You will find your Client ID, Client Secret and Domain.
credentials

Create Service Account (optional)

This is a guide to create ingestion bot service account. This step is optional if you configure the ingestion-bot with the JWT Token, you can follow the documentation of Enable JWT Tokens.

Step 1: Enable Client-Credential

  • Go to your project dashboard.
client
  • Navigate to Applications > Applications
client
  • Select your application from the list.
client
  • Once selected, scroll down until you see the Application Properties section.
  • Change the Token Endpoint Authentication Method from None to Basic.
client
  • Now scroll further down to the section on Advanced Settings.
  • Click on it and select Grant Types.
  • In the Grant Types, check the option for Client Credentials.
client
  • Once done, click on Save Changes.

Step 2: Authorize the API with our Application.

  • Navigate to Applications > APIs from the left menu.
auth
  • You will see the Auth0 Management API.
auth
  • Click on the Auth0 Management API.
auth
  • Click on the Machine to Machine Applications tab.
  • You will find your application listed below.
auth
  • Click on the toggle to authorize.
  • Once done you will find a down arrow, click on it.
auth
  • Select the permissions (scopes) that should be granted to the client.
  • Click on Update.
auth

After the applying these steps, you can update the configuration of your deployment:

{%inlineCalloutContainer%}

{%inlineCallout icon="celebration" bold="Docker Security" href="/deployment/security/auth0/docker" %} Configure Auth0 SSO for your Docker Deployment. {%/inlineCallout%}

{%inlineCallout icon="storage" bold="Bare Metal Security" href="/deployment/security/auth0/bare-metal" %} Configure Auth0 SSO for your Bare Metal Deployment. {%/inlineCallout%}

{%inlineCallout icon="fit_screen" bold="Kubernetes Security" href="/deployment/security/auth0/kubernetes" %} Configure Auth0 SSO for your Kubernetes Deployment. {%/inlineCallout%}

{%/inlineCalloutContainer%}

Configure Ingestion

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.

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

workflowConfig:
  openMetadataServerConfig:
    hostPort: "http://localhost:8585/api"
    authProvider: auth0
    securityConfig:
      clientId: "{your_client_id}"
      secretKey: "{your_client_secret}"
      domain: "{your_domain}"