Skip to main content
Version: 0.32

Integrate an auth system on Astronomer Software

Astronomer Software by default allows users to create an account with and authenticate using one of the following methods:

  • Google OAuth
  • GitHub OAuth
  • Local username/password

Authentication methods are entirely customizable. In addition to the default methods, Astronomer provides the option to integrate any provider that follows the Open Id Connect (OIDC) protocol. This includes (but is not limited to):


The following setups assume that you are using the default Astronomer implicit flow as your authorization flow. To implement a custom authorization flow, see Configure a Custom OAuth Flow.

Local auth

To let users authenticate to Astronomer with a local username and password, follow the steps below.

  1. Enable Local Auth in your config.yaml file:
enabled: true
  1. Push the configuration change to your platform as described in Apply a config change.

General OIDC configuration

If you'd like to integrate an OIDC provider with Astronomer Software, you can enable that configuration in the config.yaml file of your astronomer directory.


clockTolerance: 0 # A field that can optionally be set to adjust for clock skew on the server.
enabled: true
discoveryUrl: <provider-discovery-url> # Note this must be a URL that with an https:// prefix
clientId: <provider-client-id>
authUrlParams: # Additional required params set on case-by-case basis

Microsoft Entra ID

Replace the values above with those of the provider of your choice. If you want to configure Microsoft Entra ID, Okta or Auth0 read below for specific guidelines.

AWS Cognito

Create a user pool in Cognito

Start by creating a user pool in Cognito. You can either review the default settings or step through them to customize.

Make sure that you create an App client, which is the OpenID client configuration that we will use to authenticate against. You do not need to generate a client secret, as Astronomer is a public client that uses implicit flow.

Once the pool and app client are created, head over to the App integration >App client settings tab and configure these settings:

  • Select an identity provider to use (either the built-in cognito user pool or a federated identity provider).
  • Set the callback URL parameter to https://houston.BASEDOMAIN/v1/oauth/redirect/.
  • Enable Implicit grant in Allowed OAuth Flows. Leave the other settings disabled.
  • Enable email, openid, and profile in Allowed OAuth Scopes.

Then switch over to the Domain name tab and select a unique domain name to use for your hosted Cognito components.

Edit your Astronomer configuration

Add the following values to your config.yaml file in the astronomer/ directory:

enabled: true
clientId: <client_id>
discoveryUrl: https://cognito-idp.<AWS-REGION><COGNITO-POOL-ID>/.well-known/openid-configuration
response_type: token

Your Cognito pool ID can be found in the General settings tab of the Cognito portal. Your client ID is found in the App clients tab.

Once you've saved your config.yaml file with these values, push it to your platform. See Apply a config change.

Microsoft Entra ID

Follow these steps to configure Microsoft Entra ID as your OIDC provider.

Register the Application using App Registrations on Azure

  1. In Microsoft Entra ID, click App registrations > New registration.

  2. Complete the following sections:

    • Name: Any
    • Supported account types: Accounts in this organizational directory only (Astronomer only - single tenant)
    • Redirect URIs:
      • Web / https://houston.BASEDOMAIN/v1/oauth/redirect/.
      • Web / https://houston.BASEDOMAIN/v1/oauth/callback/.

    Replace BASEDOMAIN with your own. For example, if your base domain is, your redirect URIs should be and

  3. Click Register.

  4. Click Authentication in the left menu.

  5. In the Web area, confirm the redirect URI is correct.

  6. In the Implicit grant and hybrid flows area, select Access tokens and ID tokens.

  7. Click Save.


Create a client secret (Optional)

Complete this setup only if you want to import Microsoft Entra ID groups to Astronomer Software as Teams.

  1. In your Microsoft Entra ID application management left menu, click Certificates & secrets.

  2. Click New client secret.

  3. Enter a description in the Description field and then select an expiry period in the Expires list.

  4. Click Add.

  5. Copy the values in the Value and Secret ID columns.

  6. Click API permissions in the left menu.

  7. Click Microsoft Graph and add the following minimum permissions for Microsoft Graph:

    • email
    • Group.Read.All
    • openid
    • profile
    • User.Read

    For each of these permissions, select Grant Admin Consent for Astronomer Data. Your Microsoft Graph permissions should look similar to the following image:

    Completed permissions page in Azure

  8. Click Token configuration in the left menu.

  9. Click Add groups claim and select the following options:

    • In the Select group types to include in Access, ID, and SAML tokens area, select every option.
    • In Customize token properties by type area, expand ID, Access, and SAML and then select Group ID for each type.
  10. Click Add.

  11. Encrypt the secret value you copied as a Kubernetes Secret on your Astronomer installation. See Store and encrypt identity provider secrets.

Enable Microsoft Entra ID in your config.yaml file

Add the following values to the config.yaml file in your astronomer directory:

flow: "code"
enabled: false
enabled: true
clientId: <your-client-id>
# Configure a secret only if you're importing Microsoft Entra ID user groups as Teams
clientSecret: <your-client-secret>
audience: <your-client-id>
enabled: false

Push the configuration change to your platform. See Apply a config change.


To integrate Okta with Astronomer, you'll need to make configuration changes in Okta and Astronomer.

Okta configuration

  1. If you haven't already, create an Okta account.

  2. In your Okta account, create a new web app for Astronomer.

  3. In Okta, under General Settings > Application, set Login redirect URIs to https://houston.BASEDOMAIN/v1/oauth/redirect/, where BASEDOMAIN is the domain where you're hosting your Software installation.

  4. Under Allowed grant types, select Implicit (Hybrid).

  5. Save the Client ID generated for this Okta app for use in the next steps.

  6. Optional. To ensure that an Okta tile appears, set Initiate Login URI to https://houston.BASEDOMAIN/v1/oauth/start?provider=okta.

Enable Okta in your config.yaml file

Add the following to your config.yaml file in your astronomer directory:

enabled: true
clientId: "<okta-client-id>"
discoveryUrl: "https://<okta-base-domain>/.well-known/openid-configuration"

Then, push the configuration change to your platform as described in Apply a config change.

Note: okta-base-domain will be different from the basedomain of your Software installation. You can read Okta's docs on finding your domain if you are unsure what this value should be.


Create an Auth0 account

You'll need an Auth0 account in order to set up connections with the identity management provider of your choice. Sign up for an Auth0 account if you need to.

Create Auth0 tenant domain

When you log into Auth0 you'll be prompted to create a tenant domain. You can use the default or your own unique tenant-name. Your full tenant domain will look something like

Note: Your full tenant domain may differ if you've created it outside of the United States.

Create a connection between Auth0 and your identity management provider

Depending on the Identity Management Provider you'd like to use, the steps required to establish a connection will vary.

For instructions, navigate to Auth0's connection guides and select the identity provider of your choice. Once your connection is established, read below.

Configure Auth0 application settings

Enable / disable desired connections:

  • Navigate to<tenant-name>/applications.
  • Under Applications, select Default App.
  • Click the Connections tab. You should see your connection created in Step 3 listed here. Enable your new connection, and disable any connections that you won't be using.

Edit the Default App settings:

  • Navigate to<tenant-name>/applications.
  • Under Applications, select Default App.
  • Click the Settings tab.
  • Under Allowed Callback URLs, add https://houston.<your-astronomer-base-domain>/v1/oauth/redirect/.
  • Under Allowed Logout URLs, add https://app.<your-astronomer-base-domain>/logout.
  • Under Allowed Origins (CORS), add https://*.<your-astronomer-base-domain>.

Create Auth0 API:

  • Navigate to<tenant-name>/apis.
  • Click + Create API.
  • Under Name, enter astronomer-ee.
  • Under Identifier, enter astronomer-ee.
  • Leave the value under Signing Algorithm as RS256.

Enable Auth0 in your config.yaml file

Add the following to your config.yaml file in your astronomer directory:

enabled: true
clientId: "<default-app-client-id>"
discoveryUrl: https://<tenant-name>

Then, push the configuration change to your platform as described in Apply a config change.

Note: You can find your clientID value at<tenant-name>/applications listed next to 'Default App'.

Running behind an HTTPS proxy


Integrating an external identity provider with Astronomer requires that the platform's Houston API component is able to make outbound HTTPS requests to those identity providers in order to fetch discovery documents, sign keys, and ask for user profile information upon login/signup.

If your install is configured without a direct connection to the internet you will need to configure an HTTPS proxy server for Houston.

Configure an HTTPS proxy server for Houston

To configure the proxy server used we need to set the GLOBAL_AGENT_HTTPS_PROXY Environment Variable for the Houston deployment.

To do so, add the following to the Houston section of the config.yaml file in your astronomer directory:

enabled: true
clientId: ...
discoveryUrl: ...
value: http://my-proxy:3129

Then, push the configuration change to your platform as described in Apply a config change.

Configure a custom OAuth flow

Starting with Astronomer v0.27, you can set up a custom OAuth authorization flow as an alternative to Astronomer's default implicit flow. You can customize Astronomer's existing Okta, Google, and GitHub OAuth flows or import an entirely custom OAuth flow.


This setup must be completed only during a scheduled maintenance window. There should be no active users on your installation until the setup has been finalized.

Step 1: Configure your authorization flow on Astronomer

To use a custom Oauth authorization code flow:

  1. In your config.yaml file, set the astronomer.houston.auth.openidConnect.flow value to "code":

    # Local database (user/pass) configuration.
    enabled: true

    # Valid values are "code" and "implicit"
    flow: "code"
  2. Configure the section of your config.yaml file specific to your identity provider with each of the following values:

    • enabled: Set this value to true under the section for your own identity provider.
    • clientId and clientSecret: Your Client ID and Client secret
    • discoveryURL: Your base Discovery URL
    • authUrlParams: Additional parameters to append to your discovery URL. At a minimum, you must configure audience. Refer to your identity provider's documentation for information on how to find this value (Auth0 maintains this information in their glossary, for example).

    For example, a custom configuration of Okta might look like the following.

    enabled: true
    clientId: ffhsdf78f734h2fsd
    clientSecret: FSDFSLDFJELLGJLSDFGJL42353425
    # URL works only when IdP group imports are disabled. To import IdP groups from Okta to Software,
    # use "https://<MYIdP>" instead
    discoveryUrl: "https://<MYIdP>"
    audience: "GYHWEYHTHR443fFEW"
    1. Push your configuration changes to your platform as described in Apply a config change.

You can also pass your auth configurations as environment variables in the Houston section of your config.yaml file. If you choose to configure your installation this way, set the following variables in the astronomer.houston.env list instead of setting values in astronomer.auth:

# Replace <idp-provider> with OKTA, AUTH0, or CUSTOM
AUTH__OPENID_CONNECT__FLOW="implicit" # or "code"
AUTH__OPENID_CONNECT__CUSTOM__DISPLAY_NAME="Custom OAuth" # Only used for custom flows

For further security, you can specify the values of these environment variables as Kubernetes secrets in the astronomer.houston.secret list. See Store and encrypt identity provider secrets.

Step 2: Configure your identity provider

To finalize your configuration, configure the following key values in your identity provider's settings:

  • Grant Code: Set to "Code" or "Auth Code" depending on your identity provider.
  • Sign-in Redirect URI: Set to https://houston.<BASE_DOMAIN>/v1/oauth/callback/. Be sure to include the trailing /.

Step 3: Confirm your installation

When you complete this setup, you should be able to see the differences in login flow when logging in at <BASE_DOMAIN>

If you configured a fully custom OAuth flow, you should see a new Log in with Custom Oauth button on the Astronomer login screen:

Custom login button on the Astronomer login screen

You can see the name you configured in AUTH__OPENID_CONNECT__CUSTOM__DISPLAY_NAME when authenticating using the Astro CLI.

Manage users and Teams with SCIM

Astronomer Software supports integration with the open standard System for Cross-Domain Identity Management (SCIM). Using the SCIM protocol with Astronomer Software allows you to automatically provision and deprovision users and Teams based on templates for access and permissions. It also provides better observability through your identity provider for when users and Teams are created or modified across your organization.

This setup assumes that you have already created a web app for Astronomer Software in Okta. See Okta.

  1. In your Astronomer integration's settings page on Okta, open the General tab.

  2. Click Edit.

  3. In the Provisioning section, select SCIM.

  4. Click Save.

  5. In your Astronomer integration's settings page, open the Provisioning tab.

  6. Configure the following values for your SCIM integration.

    • SCIM connector base URL:
    • Authentication mode: Basic Auth
      • Username: <your-provisioning-account-username>
      • Password: <your-provisioning-account-password>
  7. Go to Configure API Integration and select the Enable API Integration checkbox.

  8. Go to Push Groups page and create a rule for Group Push. See Group Push.

  9. On the Assignments tab, ensure that the right users and groups in your org are assigned to the app integration. See Use the Assign Users to App action.

  10. Add the following lines to your config.yaml file:

    scimAuthCode: <your-provisioning-account-username>:<your-provisioning-account-password>
  11. Push the configuration change. See Apply a config change.

See Add SCIM provisioning to app integrations for more information about configuring SCIM within Okta.

Store and encrypt identity provider secrets

You can prevent your identity provider passwords, authorization tokens, and security keys from being exposed as plain text by encrypting them in Kubernetes secrets.

This setup is primarily used for encrypting the required secrets for configuring a custom OAuth flow.

  1. Create a file named secret.yaml that contains the value you want to encrypt as a Kubernetes secret. The following example encrypts the required client secret for configuring a custom OAuth flow for Okta.

    # Required configuration for all secrets
    kind: Secret
    apiVersion: v1
    name: okta-secret
    release: {{ .Release.Name }}
    chart: {{ .Chart.Name }}
    heritage: {{ .Release.Service }}
    component: {{ template "houston.backendSecret" . }}
    type: Opaque
    # Specify a key and value for the data you want to encrypt
    okta_client_secret: {{ "<okta-secret-value>" | b64enc | quote }}
  2. Run the following command to apply your secret to your Astronomer cluster:

    kubectl apply -f ./secret.yaml
  3. Reference your secret name, key, and the environment variable you want the key to apply towards in your config.yaml file. To configure the example secret from Step 1 as an Okta client secret, you would add the following:

    secretName: "okta-secret"
    secretKey: "okta_client_secret"
  4. Save and push your changes. See Apply a config change.

Was this page helpful?

Sign up for Developer Updates

Get a summary of new Astro features once a month.

You can unsubscribe at any time.
By proceeding you agree to our Privacy Policy, our Website Terms and to receive emails from Astronomer.