OpenMetadata/openmetadata-docs/content/v1.5.x/deployment/security/azure/bare-metal.md

title	slug	collate
Azure SSO for Bare Metal	/deployment/security/azure/bare-metal	false

Azure SSO for Bare Metal

Get the Client Id and Tenant ID from Azure Application configured in Step 3.

Update conf/openmetadata.yaml

authenticationConfiguration:
  provider: "azure"
  publicKeyUrls:
    - "https://login.microsoftonline.com/common/discovery/keys"
    - "https://{your domain}/api/v1/system/config/jwks" # Update with your Domain and Make sure this "/api/v1/system/config/jwks" is always configured to enable JWT tokens
  authority: "https://login.microsoftonline.com/{Tenant ID}"
  clientId: "{Client ID}" # Azure Application
  callbackUrl: "https://{your domain}/callback"

Then,

• Update authorizerConfiguration to add login names of the admin users in adminPrincipals section as shown below.
• Update the principalDomain to your company domain name.

{% note %}

AUTHENTICATION_PUBLIC_KEYS and AUTHENTICATION_CALLBACK_URL refers to https://{your domain} this is referring to your OpenMetdata installation domain name and please make sure to correctly put http or https depending on your installation.

{% /note %}

{% note %}

Altering the order of claims in jwtPrincipalClaims may lead to problems when matching a user from a token with an existing user in the system. The mapping process relies on the specific order of claims, so changing it can result in inconsistencies or authentication failures, as the system cannot ensure correct user mapping with a new claim order.

{% /note %}

authorizerConfiguration:
  className: "org.openmetadata.service.security.DefaultAuthorizer"
  # JWT Filter
  containerRequestFilter: "org.openmetadata.service.security.JwtFilter"
  adminPrincipals:
    - "user1"
    - "user2"
  principalDomain: "open-metadata.org"

{% partial file="/v1.5/deployment/configure-ingestion.md" /%}