How to Set Up OIDC for Amundsen Using Auth0

May 20th, 2022

header image for How to Set Up OIDC for Amundsen Using Auth0

Setting up OIDC for Amundsen using Auth0

Amundsen natively supports setting up OIDC-based authentication. Using a few modifications to the Amundsen frontend service, you can enable OIDC using an identity provider. This article will take you through setting up OIDC for Amundsen using Auth0.

Five steps to setup OIDC for Amundsen using Auth0

  1. Setup Amundsen
  2. Create a Single-Page Application on Auth0
  3. Configure Amundsen to use Auth0
  4. Rebuild the frontend to integrate FlaskOIDC and deploy
  5. Log into Amundsen using Auth0

Step 1: Install Amundsen

Clone the GitHub repository

You can use the following command to clone Amundsen’s GitHub repository:

$ git clone --recursive

Create a new branch where you’ll make the changes:

$ git checkout -b feature/add-auth0-oidc

Install Docker Engine and Docker Compose

If you don’t already have it installed, you need to install the Docker Engine and Docker Compose on your machine.

After completing the installation, use the docker-amundsen-atlas.yml file to deploy Amundsen using Docker:

$ docker-compose -f docker-amundsen-local.yml up

Read more: Detailed overview of the Amundsen installation process

Step 2: Create a Single-Page Application on Auth0

Create an application

Sign up and log into your Auth0 account. To enable authentication redirection from Amundsen to Auth0, you need to create an application. Go to the left panel on your Auth0 home page and click on Application. Now, use the Create Application button on the upper right corner of the page to create a single-page web application, as shown in the image below:

Create a new application in Auth0

Create a new application in Auth0

This single-page application will be able to receive and respond to requests that are required to complete the authentication.

Client ID and Client Secret

You'll land upon the Quick Start page as soon as you create the application. As you’re using Amundsen, which already has the support for external authentication mechanisms, you can skip it and move straight to the Settings page, as shown below:

Create Client ID and Client Secret

Create Client ID and Client Secret

For a basic setup, most of the defaults are good enough. You will need to copy the Client ID and the Client Secret and provide these as environment variables or a config file to Amundsen so that Amundsen is authorized to make authentication requests.

Set Application URIs

To enable Auth0 to direct a user to the Amundsen application both for authentication and redirection after a user gets authenticated, you will need to provide the following three URIs:

  • Application Login URI — to enable Auth0 to direct you to Amundsen’s login page.
  • Allowed Callback URLs — to enable Auth0 to direct you to your application after the authentication completes successfully.
  • Allowed Logout URLs — to enable Auth0 to log you out of Amundsen.

In the following image, you can see that Amundsen is locally hosted on and port 5000, with the URIs as mentioned earlier, populated accordingly:

Set Application login URI

Set Application login URI

Please note that your Amundsen application must be up and running when you add and save these URIs; otherwise, Auth0 won’t be able to verify them. You can learn about application settings by visiting Auth0’s official documentation.

Google OAuth 2.0

Auth0 comes with a default Google OAuth and Username-Password-based authentication method. The Google OAuth connection is great if your organization uses Google Workspace.

Enable Google OAuth

Enable Google OAuth

Step 3: Configure Amundsen to use Auth0

Install FlaskOIDC

Amundsen frontend already supports FlaskOIDC out-of-the-box, so configuring it is pretty straightforward. You can either install FlaskOIDC manually by running the following command or add it to the one of the requirements*.txt files:

$ pip3 install flaskoidc

As you have already set up the single-page application in the previous setup, you must now have the following information stored in a .env file so that you can source it and the values are available as environment variables:

export FLASK_APP_MODULE_NAME=flaskoidc

##setup FRONTEND_SVC_CONFIG_MODULE_CLASS to invoke OidcConfig module ./amundsen_application/
export FRONTEND_SVC_CONFIG_MODULE_CLASS='amundsen_application.oidc_config.OidcConfig'

##setup flaskoidc for ./amundsen_application/
export APP_WRAPPER=flaskoidc

export SQLALCHEMY_DATABASE_URI='sqlite:///sessions.db'

export SESSION_TYPE='sqlalchemy'

export FLASK_OIDC_SECRET_KEY='base-flask-oidc-secret-key'

export FLASK_OIDC_WHITELISTED_ENDPOINTS="status,healthcheck,health"
export FLASK_OIDC_LOG_DATE_FORMAT='%Y-%m-%dT%H:%M:%S%z'

export OIDC_CLIENT_SECRETS='./client_secrets.json'

export OIDC_CALLBACK_ROUTE='/authorization-code/callback'
export OIDC_DEBUG=True

export FLASK_OIDC_CLIENT_ID='4wORqNIVC2HfXdout8b2fHXDwlhhaHlW'
export FLASK_OIDC_CLIENT_SECRET='NLFppVr-aJh19AEjsm0axsmPkBs-1VGbeQU0raENy2NjQ6FaMX3h1yh0YuXdKUaF'
export FLASK_OIDC_REDIRECT_URI='/authorization-code/callback'

Amundsen can also pick up some of these variables from a JSON file, the path to which you’ll have to mention in an environment variable —  OIDC_CLIENT_SECRETS. You can get the following JSON file from the following URL [](

    "issuer": "",
    "authorization_endpoint": "",
    "token_endpoint": "",
    "device_authorization_endpoint": "",
    "userinfo_endpoint": "",
    "mfa_challenge_endpoint": "",
    "jwks_uri": "",
    "registration_endpoint": "",
    "revocation_endpoint": "",
    "scopes_supported": ["openid", "profile", "offline_access", "name", "given_name", "family_name", "nickname", "email", "email_verified", "picture", "created_at", "identities", "phone", "address"],
    "response_types_supported": ["code", "token", "id_token", "code token", "code id_token", "token id_token", "code token id_token"],
    "code_challenge_methods_supported": ["S256", "plain"],
    "response_modes_supported": ["query", "fragment", "form_post"],
    "subject_types_supported": ["public"],
    "id_token_signing_alg_values_supported": ["HS256", "RS256"],
    "token_endpoint_auth_methods_supported": ["client_secret_basic", "client_secret_post"],
    "claims_supported": ["aud", "auth_time", "created_at", "email", "email_verified", "exp", "family_name", "given_name", "iat", "identities", "iss", "name", "nickname", "phone_number", "picture", "sub"],
    "request_uri_parameter_supported": false,

Note that client_id and client_secret have been added later to this secrets file.

Step 4: Rebuild the frontend to integrate FlaskOIDC

Build static content

Once all the required environment variables and secrets are in place, you can build the static content used by Amundsen’s frontend service by running the following set of commands:

$ cd amundsen/frontend/amundsen_application/static
$ npm install
$ npm run build
$ cd ../../

Build the Flask app

As mentioned earlier, you can either install FlaskOIDC manually or add it to the list of dependencies. Once you do that, you can run the following commands to complete the frontend build that allows Auth0 to interact with Amundsen using FlaskOIDC:

$ python3 -m venv venv
$ source venv/bin/activate
$ pip3 install -e ".[all]" .

Start Amundsen frontend in standalone mode

To make sure that all your configurations are correct, rather than building all of Amundsen’s services, you can start the Amundsen frontend service in standalone mode using the following command:

$ python3 amundsen_application/

Before you run the command, you need to stop the currently deployed Docker containers. After stopping the Docker container, if you see that the frontend service is running on a different local IP address and port than you previously specified in the environment variables and the Auth0 app, you’ll need to update them before expecting the authentication to work.

If everything’s in order, you can now build Amundsen using Docker.

Build and deploy Docker images after local changes

Building static content and deploying the Flask app is one way to go, but you can also use the docker-amundsen-local.yml file to build and test local changes to your Amundsen application, using the following commands:

$ docker-compose -f docker-amundsen-local.yml build
$ docker-compose -f docker-amundsen-local.yml up -d

Step 5: Log into Amundsen using OIDC auth

Once your Amundsen containers are up and running, you can log onto the local IP address; in this case,, and you can expect Amundsen to redirect you to the Auth0 authentication page, as shown in the image below:

Log into Amundsen using OIDC auth

Log into Amundsen using OIDC auth

You can sign up and log in using a username and password or log in using Google. You can also check the logs in your terminal to understand the steps of the authentication more:

Check logs to understand the steps of authentication

Check logs to understand the steps of authentication

You are now ready to use Amundsen more securely than before.


Payload Validation Error with HTTP

Amundsen’s default deployment uses HTTP and not HTTPS, but Auth0 requires the Application Login URI to be HTTPS; otherwise, you will see the following error saying that the initiate login URI must be HTTPS:

Payload Validation Error with HTTP

Payload Validation Error with HTTP

Fortunately, you don’t have to worry about Amundsen not using HTTPS; you can just change the URI from []( to [](, and your browser will take care of the rest.

Callback URL Mismatch Error

Another common error is when your callback URL doesn’t exactly match the local IP address where you’ve hosted your Amundsen. As mentioned above, the IP address of the Amundsen application in this example is, so rather than using localhost, you’ll need to use the actual local IP address, be it,,, and so on. If there’s a mismatch, you’ll see the error shown below:

Callback URL Mismatch Error

Callback URL Mismatch Error

You can also see more details about the error by viewing the application logs on the console, as shown in the image below:

Check application logs for more details on the error

Check application logs for more details on the error

Auth0 documentation is straightforward to navigate. If you encounter any other issues, they won’t be hard to debug and fix.


Amundsen comes with many out-of-the-box features that you need to configure yourself by making a few code changes. Making Amundsen use Auth0 doesn’t take a lot of code changes; it just requires you to install a library, add a few variables, and create an Auth0 account. You can use any OIDC-based identity provider, such as Okta, PingIdentity, etc., for securing your Amundsen deployment with just the steps mentioned in this guide.

Amundsen demo: Get hands-on

This blog is part of a series of blogs where we are discussing steps to setup Amundsen  as a data catalog for your team. In case you don't want to go through this entire process and want to quickly browse through the Amundsen experience, we've set up a sample demo environment for you, feel free to explore:

Click to try Amundsen

If you are a data consumer or producer and are looking to champion your organization to optimally utilize the value of your modern data stack — while weighing your build vs buy option — it’s worth taking a look at off-the-shelf alternatives like Atlan — A data catalog and metadata management tool built for the modern data teams.

"It would take six or seven people up to two years to build what Atlan gave us out of the box. We needed a solution on day zero, not in a year or two."

Akash Deep Verma
Akash Deep Verma

Director of Data Engineering

Delhivery: Leading fulfilment platform for digital commerce.

Build vs Buy: Delhivery’s Learnings from Implementing a Data Catalog

Build vs Buy: Delhivery’s Learnings from Implementing a Data Catalog