yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-10-12 09:18:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

SSO Docker - changed to Bash from YAML (#6611)

Browse Source
This commit is contained in:
Shilpa Vernekar 2022-08-05 23:03:33 +05:30 committed by GitHub
parent a90787c54a
commit 29248437c3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
11 changed files with 102 additions and 110 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
openmetadata-docs/content/deployment/security/amazon-cognito-sso/docker.md
View File

@ -9,7 +9,7 @@ To enable security for the Docker deployment, follow the next steps:
## 1. Create an .env file ## 1. Create an .env file
Create an `openmetadata.env` file and add the following contents as an example. Use the information Create an `openmetadata_cognito.env` file and add the following contents as an example. Use the information
generated when setting up the account in the previous steps. generated when setting up the account in the previous steps.
```bash ```bash
@ -21,9 +21,9 @@ AUTHORIZER_INGESTION_PRINCIPALS=[ingestion-bot]
AUTHORIZER_PRINCIPAL_DOMAIN=open-metadata.org # Update with your domain AUTHORIZER_PRINCIPAL_DOMAIN=open-metadata.org # Update with your domain
AUTHENTICATION_PROVIDER=aws-cognito AUTHENTICATION_PROVIDER=aws-cognito
AUTHENTICATION_PUBLIC_KEYS=[https://cognito-idp.us-west-1.amazonaws.com/{User Pool ID}/.well-known/jwks.json] AUTHENTICATION_PUBLIC_KEYS=[{Cognito Domain}/{User Pool ID}/.well-known/jwks.json] # Update with your Cognito Domain and User Pool ID
AUTHENTICATION_AUTHORITY=https://cognito-idp.us-west-1.amazonaws.com/{User Pool ID} AUTHENTICATION_AUTHORITY={Cognito Domain}/{User Pool ID} # Update with your Cognito Domain and User Pool ID as follows - https://cognito-idp.us-west-1.amazonaws.com/us-west-1_DL8xfTzj8
AUTHENTICATION_CLIENT_ID={Client ID} AUTHENTICATION_CLIENT_ID={Client ID} # Update with your Client ID
AUTHENTICATION_CALLBACK_URL=http://localhost:8585/callback AUTHENTICATION_CALLBACK_URL=http://localhost:8585/callback
# Airflow Configuration # Airflow Configuration

31
openmetadata-docs/content/deployment/security/auth0/docker.md
View File

@ -12,26 +12,25 @@ To enable security for the Docker deployment, follow the next steps:
Create an `openmetadata_auth0.env` file and add the following contents as an example. Use the information Create an `openmetadata_auth0.env` file and add the following contents as an example. Use the information
generated when setting up the account. generated when setting up the account.
```yaml ```shell
# OpenMetadata Server Authentication Configuration # OpenMetadata Server Authentication Configuration
AUTHORIZER_CLASS_NAME: org.openmetadata.catalog.security.DefaultAuthorizer AUTHORIZER_CLASS_NAME=org.openmetadata.catalog.security.DefaultAuthorizer
AUTHORIZER_REQUEST_FILTER: org.openmetadata.catalog.security.JwtFilter AUTHORIZER_REQUEST_FILTER=org.openmetadata.catalog.security.JwtFilter
AUTHORIZER_ADMIN_PRINCIPALS: [ admin ] # Your `name` from name@domain.com AUTHORIZER_ADMIN_PRINCIPALS=[admin] # Your `name` from name@domain.com
AUTHORIZER_INGESTION_PRINCIPALS: [ ingestion-bot ] AUTHORIZER_INGESTION_PRINCIPALS=[ingestion-bot]
AUTHORIZER_PRINCIPAL_DOMAIN: open-metadata.org AUTHORIZER_PRINCIPAL_DOMAIN=open-metadata.org # Update with your domain
AUTHENTICATION_PROVIDER: auth0 AUTHENTICATION_PROVIDER=auth0
AUTHENTICATION_PUBLIC_KEYS: AUTHENTICATION_PUBLIC_KEYS=[{Domain}/.well-known/jwks.json] # Update with your Domain
- "https://parth-panchal.us.auth0.com/.well-known/jwks.json" AUTHENTICATION_AUTHORITY={Domain} # Update with your Domain
AUTHENTICATION_AUTHORITY: "https://parth-panchal.us.auth0.com/" AUTHENTICATION_CLIENT_ID={Client ID} # Update with your Client ID
AUTHENTICATION_CLIENT_ID: Client ID AUTHENTICATION_CALLBACK_URL=http://localhost:8585/callback
AUTHENTICATION_CALLBACK_URL: http://localhost:8585/callback
# Airflow Configuration # Airflow Configuration
AIRFLOW_AUTH_PROVIDER: auth0 AIRFLOW_AUTH_PROVIDER=auth0
OM_AUTH_AIRFLOW_AUTH0_CLIENT_ID: Client ID OM_AUTH_AIRFLOW_AUTH0_CLIENT_ID={Client ID} # Update with your Client ID
OM_AUTH_AIRFLOW_AUTH0_CLIENT_SECRET: Client Secret OM_AUTH_AIRFLOW_AUTH0_CLIENT_SECRET={Client Secret} # Update with your Client Secret
OM_AUTH_AIRFLOW_AUTH0_DOMAIN_URL: Domain OM_AUTH_AIRFLOW_AUTH0_DOMAIN_URL={Domain} # Update with your Domain
``` ```
## 2. Start Docker ## 2. Start Docker

35
openmetadata-docs/content/deployment/security/azure/docker.md
View File

@ -12,29 +12,26 @@ To enable security for the Docker deployment, follow the next steps:
Create an `openmetadata_azure.env` file and add the following contents as an example. Use the information Create an `openmetadata_azure.env` file and add the following contents as an example. Use the information
generated when setting up the account. generated when setting up the account.
```yaml ```shell
# OpenMetadata Server Authentication Configuration # OpenMetadata Server Authentication Configuration
AUTHORIZER_CLASS_NAME: org.openmetadata.catalog.security.DefaultAuthorizer AUTHORIZER_CLASS_NAME=org.openmetadata.catalog.security.DefaultAuthorizer
AUTHORIZER_REQUEST_FILTER: org.openmetadata.catalog.security.JwtFilter AUTHORIZER_REQUEST_FILTER=org.openmetadata.catalog.security.JwtFilter
AUTHORIZER_ADMIN_PRINCIPALS: [ admin ] # Your `name` from name@domain.com AUTHORIZER_ADMIN_PRINCIPALS=[admin] # Your `name` from name@domain.com
AUTHORIZER_INGESTION_PRINCIPALS: [ ingestion-bot ] AUTHORIZER_INGESTION_PRINCIPALS=[ingestion-bot]
AUTHORIZER_PRINCIPAL_DOMAIN: open-metadata.org AUTHORIZER_PRINCIPAL_DOMAIN=open-metadata.org # Update with your domain
AUTHENTICATION_PROVIDER: azure AUTHENTICATION_PROVIDER=azure
AUTHENTICATION_PUBLIC_KEYS: AUTHENTICATION_PUBLIC_KEYS=[https://login.microsoftonline.com/common/discovery/keys]
- "https://login.microsoftonline.com/common/discovery/keys" AUTHENTICATION_AUTHORITY=https://login.microsoftonline.com/{Tenant ID} # Update with your Tenant ID
AUTHENTICATION_AUTHORITY: "https://login.microsoftonline.com/{Tenant ID}" AUTHENTICATION_CLIENT_ID={Client ID} # Update with your Client ID
AUTHENTICATION_CLIENT_ID: Client ID AUTHENTICATION_CALLBACK_URL=http://localhost:8585/callback
AUTHENTICATION_CALLBACK_URL: http://localhost:8585/callback
# Airflow Configuration # Airflow Configuration
AIRFLOW_AUTH_PROVIDER: azure AIRFLOW_AUTH_PROVIDER=azure
OM_AUTH_AIRFLOW_AZURE_CLIENT_SECRET: Client Secret OM_AUTH_AIRFLOW_AZURE_CLIENT_SECRET={Client Secret} # Update with your Client Secret
OM_AUTH_AIRFLOW_AZURE_AUTHORITY_URL: "https://login.microsoftonline.com/{Tenant ID}" OM_AUTH_AIRFLOW_AZURE_AUTHORITY_URL=https://login.microsoftonline.com/{Tenant ID} # Update with your Tenant ID
OM_AUTH_AIRFLOW_AZURE_SCOPES: OM_AUTH_AIRFLOW_AZURE_SCOPES=[{scopes}] # Update with your Scopes
- scope 1 OM_AUTH_AIRFLOW_AZURE_CLIENT_ID={Client Id} # Update with your Client ID
- scope 2
OM_AUTH_AIRFLOW_AZURE_CLIENT_ID: Client Id
``` ```
## 2. Start Docker ## 2. Start Docker

35
openmetadata-docs/content/deployment/security/custom-oidc/docker.md
View File

@ -9,32 +9,31 @@ To enable security for the Docker deployment, follow the next steps:
## 1. Create an .env file ## 1. Create an .env file
Create an `openmetadata_azure.env` file and add the following contents as an example. Use the information Create an `openmetadata_oidc.env` file and add the following contents as an example. Use the information
generated when setting up the account. generated when setting up the account.
```yaml ```shell
# OpenMetadata Server Authentication Configuration # OpenMetadata Server Authentication Configuration
AUTHORIZER_CLASS_NAME: org.openmetadata.catalog.security.DefaultAuthorizer AUTHORIZER_CLASS_NAME=org.openmetadata.catalog.security.DefaultAuthorizer
AUTHORIZER_REQUEST_FILTER: org.openmetadata.catalog.security.JwtFilter AUTHORIZER_REQUEST_FILTER=org.openmetadata.catalog.security.JwtFilter
AUTHORIZER_ADMIN_PRINCIPALS: [ admin ] # Your `name` from name@domain.com AUTHORIZER_ADMIN_PRINCIPALS=[admin] # Your `name` from name@domain.com
AUTHORIZER_INGESTION_PRINCIPALS: [ ingestion-bot ] AUTHORIZER_INGESTION_PRINCIPALS=[ingestion-bot]
AUTHORIZER_PRINCIPAL_DOMAIN: open-metadata.org AUTHORIZER_PRINCIPAL_DOMAIN=open-metadata.org # Update with your domain
AUTHENTICATION_PROVIDER: custom-oidc AUTHENTICATION_PROVIDER=custom-oidc
CUSTOM_OIDC_AUTHENTICATION_PROVIDER_NAME: KeyCloak CUSTOM_OIDC_AUTHENTICATION_PROVIDER_NAME=KeyCloak
AUTHENTICATION_PUBLIC_KEYS: AUTHENTICATION_PUBLIC_KEYS=[{http://localhost:8080/realms/myrealm/protocol/openid-connect/certs}]
- "http://localhost:8080/realms/myrealm/protocol/openid-connect/certs" AUTHENTICATION_AUTHORITY={http://localhost:8080/realms/myrealm}
AUTHENTICATION_AUTHORITY: "http://localhost:8080/realms/myrealm" AUTHENTICATION_CLIENT_ID={Client ID} # Update with your Client ID
AUTHENTICATION_CLIENT_ID: Client ID AUTHENTICATION_CALLBACK_URL=http://localhost:8585/callback
AUTHENTICATION_CALLBACK_URL: http://localhost:8585/callback
# Airflow Configuration # Airflow Configuration
AIRFLOW_AUTH_PROVIDER: custom-oidc AIRFLOW_AUTH_PROVIDER=custom-oidc
OM_AUTH_AIRFLOW_CUSTOM_OIDC_CLIENT_ID: Client Id OM_AUTH_AIRFLOW_CUSTOM_OIDC_CLIENT_ID={Client Id} # Update with your Client ID
# Make sure to add the path where the file is saved in the Airflow Volume # Make sure to add the path where the file is saved in the Airflow Volume
# It needs to be reachable locally by the container # It needs to be reachable locally by the container
OM_AUTH_AIRFLOW_CUSTOM_OIDC_SECRET_KEY_PATH: Secret Key Path OM_AUTH_AIRFLOW_CUSTOM_OIDC_SECRET_KEY_PATH={Secret Key Path} # Update with your Secret Key Path
OM_AUTH_AIRFLOW_CUSTOM_OIDC_TOKEN_ENDPOINT_URL: endpoint OM_AUTH_AIRFLOW_CUSTOM_OIDC_TOKEN_ENDPOINT_URL={endpoint}
``` ```
## 2. Start Docker ## 2. Start Docker

2
openmetadata-docs/content/deployment/security/google/docker.md
View File

@ -9,7 +9,7 @@ To enable security for the Docker deployment, follow the next steps:
## 1. Create an .env file ## 1. Create an .env file
Create an `openmetadata.env` file and add the following contents as an example. Use the information Create an `openmetadata_google.env` file and add the following contents as an example. Use the information
generated when setting up the account in the previous steps. generated when setting up the account in the previous steps.
```bash ```bash

11
openmetadata-docs/content/deployment/security/index.md
View File

@ -7,10 +7,9 @@ slug: /deployment/security
This section provides detailed instructions to secure the REST endpoints of the OpenMetadata Server. This section provides detailed instructions to secure the REST endpoints of the OpenMetadata Server.
OpenMetadata has support for Google SSO, Okta SSO, custom OIDC, Auth0, and Azure SSO as identity providers. Please see OpenMetadata has support for Google SSO, Okta SSO, custom OIDC, Auth0, Azure SSO, Amazon Cognito, and OneLogin as identity providers. Please see the next sections about how to configure them.
the next sections about how to configure them.
Enabling Security is only required for your **Production** installation. If you are testing OpenMetadata it will be easier Enabling Security is only required for your **Production** installation. If you are testing OpenMetadata, it will be easier
and faster to set up without security. To get up and running quickly with OpenMetadata (without security), and faster to set up without security. To get up and running quickly with OpenMetadata (without security),
please follow the [Quickstart](/quick-start/local-deployment) guide. please follow the [Quickstart](/quick-start/local-deployment) guide.
@ -61,14 +60,14 @@ please follow the [Quickstart](/quick-start/local-deployment) guide.
icon="add_moderator" icon="add_moderator"
href="/deployment/security/amazon-cognito" href="/deployment/security/amazon-cognito"
> >
Configure Okta SSO to access the UI and APIs Configure Amazon Cognito SSO to access the UI and APIs
</InlineCallout> </InlineCallout>
<InlineCallout <InlineCallout
color="violet-70" color="violet-70"
bold="One Login SSO" bold="OneLogin SSO"
icon="add_moderator" icon="add_moderator"
href="/deployment/security/one-login" href="/deployment/security/one-login"
> >
Configure One Login SSO to access the UI and APIs Configure OneLogin SSO to access the UI and APIs
</InlineCallout> </InlineCallout>
</InlineCalloutContainer> </InlineCalloutContainer>

37
openmetadata-docs/content/deployment/security/okta/docker.md
View File

@ -9,31 +9,30 @@ To enable security for the Docker deployment, follow the next steps:
## 1. Create an .env file ## 1. Create an .env file
Create an `openmetadata_azure.env` file and add the following contents as an example. Use the information Create an `openmetadata_okta.env` file and add the following contents as an example. Use the information
generated when setting up the account. generated when setting up the account.
```yaml ```shell
# OpenMetadata Server Authentication Configuration # OpenMetadata Server Authentication Configuration
AUTHORIZER_CLASS_NAME: org.openmetadata.catalog.security.DefaultAuthorizer AUTHORIZER_CLASS_NAME=org.openmetadata.catalog.security.DefaultAuthorizer
AUTHORIZER_REQUEST_FILTER: org.openmetadata.catalog.security.JwtFilter AUTHORIZER_REQUEST_FILTER=org.openmetadata.catalog.security.JwtFilter
AUTHORIZER_ADMIN_PRINCIPALS: [ admin ] # Your `name` from name@domain.com AUTHORIZER_ADMIN_PRINCIPALS=[admin] # Your `name` from name@domain.com
AUTHORIZER_INGESTION_PRINCIPALS: [ ingestion-bot ] AUTHORIZER_INGESTION_PRINCIPALS=[ingestion-bot]
AUTHORIZER_PRINCIPAL_DOMAIN: open-metadata.org AUTHORIZER_PRINCIPAL_DOMAIN=open-metadata.org # Update with your domain
AUTHENTICATION_PROVIDER: okta AUTHENTICATION_PROVIDER=okta
AUTHENTICATION_PUBLIC_KEYS: AUTHENTICATION_PUBLIC_KEYS={ISSUER_URL}/v1/keys # Update with your Issuer URL
- "{ISSUER_URL}/v1/keys" AUTHENTICATION_AUTHORITY={ISSUER_URL} # Update with your Issuer URL
AUTHENTICATION_AUTHORITY: "{ISSUER_URL}" AUTHENTICATION_CLIENT_ID={CLIENT_ID - SPA APP} # Update with your Client ID
AUTHENTICATION_CLIENT_ID: "{CLIENT_ID - SPA APP}" AUTHENTICATION_CALLBACK_URL=http://localhost:8585/callback
AUTHENTICATION_CALLBACK_URL: http://localhost:8585/callback
# Airflow Configuration # Airflow Configuration
AIRFLOW_AUTH_PROVIDER: okta AIRFLOW_AUTH_PROVIDER=okta
OM_AUTH_AIRFLOW_OKTA_CLIENT_ID: ${OM_AUTH_AIRFLOW_OKTA_CLIENT_ID:-""} OM_AUTH_AIRFLOW_OKTA_CLIENT_ID={OM_AUTH_AIRFLOW_OKTA_CLIENT_ID:-""}
OM_AUTH_AIRFLOW_OKTA_ORGANIZATION_URL: ${OM_AUTH_AIRFLOW_OKTA_ORGANIZATION_URL:-""} OM_AUTH_AIRFLOW_OKTA_ORGANIZATION_URL={OM_AUTH_AIRFLOW_OKTA_ORGANIZATION_URL:-""}
OM_AUTH_AIRFLOW_OKTA_PRIVATE_KEY: ${OM_AUTH_AIRFLOW_OKTA_PRIVATE_KEY:-""} OM_AUTH_AIRFLOW_OKTA_PRIVATE_KEY={OM_AUTH_AIRFLOW_OKTA_PRIVATE_KEY:-""}
OM_AUTH_AIRFLOW_OKTA_SA_EMAIL: ${OM_AUTH_AIRFLOW_OKTA_SA_EMAIL:-""} OM_AUTH_AIRFLOW_OKTA_SA_EMAIL={OM_AUTH_AIRFLOW_OKTA_SA_EMAIL:-""}
OM_AUTH_AIRFLOW_OKTA_SCOPES: ${OM_AUTH_AIRFLOW_OKTA_SCOPES:-[]} OM_AUTH_AIRFLOW_OKTA_SCOPES={OM_AUTH_AIRFLOW_OKTA_SCOPES:-[]}
``` ```
## 2. Start Docker ## 2. Start Docker

8
openmetadata-docs/content/deployment/security/one-login/bare-metal.md
View File

@ -1,22 +1,22 @@
--- ---
title: One Login SSO for Bare Metal title: OneLogin SSO for Bare Metal
slug: /deployment/security/one-login/bare-metal slug: /deployment/security/one-login/bare-metal
--- ---
# One Login SSO for Bare Metal # OneLogin SSO for Bare Metal
## Update conf/openmetadata.yaml ## Update conf/openmetadata.yaml
Once the `Client Id` and `Client Secret` are generated add the `Client Id` in `openmetadata.yaml` file in `client_id` field. Once the `Client Id` and `Client Secret` are generated add the `Client Id` in `openmetadata.yaml` file in `client_id` field.
Update the providerName config to the name you want to display in the `Sign In` button in the UI. Update the providerName config to the name you want to display in the `Sign In` button in the UI.
For example, with the following configuration with `providerName` set to `One Login`, the users will see `Sign In with One Login SSO` For example, with the following configuration with `providerName` set to `OneLogin`, the users will see `Sign In with OneLogin SSO`
in the `Sign In` page of the OpenMetadata UI. in the `Sign In` page of the OpenMetadata UI.
```yaml ```yaml
authenticationConfiguration: authenticationConfiguration:
provider: "custom-oidc" provider: "custom-oidc"
providerName: "One Login" providerName: "OneLogin"
publicKeyUrls: publicKeyUrls:
- "{IssuerUrl}/certs" - "{IssuerUrl}/certs"
authority: "{IssuerUrl}" authority: "{IssuerUrl}"

31
openmetadata-docs/content/deployment/security/one-login/docker.md
View File

@ -12,28 +12,27 @@ To enable security for the Docker deployment, follow the next steps:
Create an `openmetadata_onelogin.env` file and add the following contents as an example. Use the information Create an `openmetadata_onelogin.env` file and add the following contents as an example. Use the information
generated when setting up the account. generated when setting up the account.
```yaml ```shell
# OpenMetadata Server Authentication Configuration # OpenMetadata Server Authentication Configuration
AUTHORIZER_CLASS_NAME: org.openmetadata.catalog.security.DefaultAuthorizer AUTHORIZER_CLASS_NAME=org.openmetadata.catalog.security.DefaultAuthorizer
AUTHORIZER_REQUEST_FILTER: org.openmetadata.catalog.security.JwtFilter AUTHORIZER_REQUEST_FILTER=org.openmetadata.catalog.security.JwtFilter
AUTHORIZER_ADMIN_PRINCIPALS: [ admin ] # Your `name` from name@domain.com AUTHORIZER_ADMIN_PRINCIPALS=[admin] # Your `name` from name@domain.com
AUTHORIZER_INGESTION_PRINCIPALS: [ ingestion-bot ] AUTHORIZER_INGESTION_PRINCIPALS=[ingestion-bot]
AUTHORIZER_PRINCIPAL_DOMAIN: open-metadata.org AUTHORIZER_PRINCIPAL_DOMAIN=open-metadata.org # Update with your domain
AUTHENTICATION_PROVIDER: custom-oidc AUTHENTICATION_PROVIDER=custom-oidc
AUTHENTICATION_PUBLIC_KEYS: AUTHENTICATION_PUBLIC_KEYS={public key url} # Update with your Public Key URL
- {public key url} AUTHENTICATION_AUTHORITY={issuer url} # Update with your Issuer URL
AUTHENTICATION_AUTHORITY: {issuer url} AUTHENTICATION_CLIENT_ID={Client ID} # Update with your Client ID
AUTHENTICATION_CLIENT_ID: {Client ID} AUTHENTICATION_CALLBACK_URL=http://localhost:8585/callback
AUTHENTICATION_CALLBACK_URL: http://localhost:8585/callback
# Airflow Configuration # Airflow Configuration
AIRFLOW_AUTH_PROVIDER: custom-oidc AIRFLOW_AUTH_PROVIDER=custom-oidc
OM_AUTH_AIRFLOW_CUSTOM_OIDC_CLIENT_ID: Client Id OM_AUTH_AIRFLOW_CUSTOM_OIDC_CLIENT_ID=Client Id # Update with your Client ID
# Make sure to add the path where the file is saved in the Airflow Volume # Make sure to add the path where the file is saved in the Airflow Volume
# It needs to be reachable locally by the container # It needs to be reachable locally by the container
OM_AUTH_AIRFLOW_CUSTOM_OIDC_SECRET_KEY_PATH: Secret Key Path OM_AUTH_AIRFLOW_CUSTOM_OIDC_SECRET_KEY_PATH=Secret Key Path # Update with your Secret Key Path
OM_AUTH_AIRFLOW_CUSTOM_OIDC_TOKEN_ENDPOINT_URL: endpoint OM_AUTH_AIRFLOW_CUSTOM_OIDC_TOKEN_ENDPOINT_URL=endpoint
``` ```
## 2. Start Docker ## 2. Start Docker

12
openmetadata-docs/content/deployment/security/one-login/index.md
View File

@ -1,11 +1,11 @@
--- ---
title: One Login SSO title: OneLogin SSO
slug: /deployment/security/one-login slug: /deployment/security/one-login
--- ---
# One Login SSO # OneLogin SSO
Follow the sections in this guide to set up One Login SSO. Follow the sections in this guide to set up OneLogin SSO.
<Collapse title="Create Server Credentials"> <Collapse title="Create Server Credentials">
@ -65,7 +65,7 @@ After the applying these steps, you can update the configuration of your deploym
bold="Docker Security" bold="Docker Security"
href="/deployment/security/one-login/docker" href="/deployment/security/one-login/docker"
> >
Configure One Login SSO for your Docker Deployment. Configure OneLogin SSO for your Docker Deployment.
</InlineCallout> </InlineCallout>
<InlineCallout <InlineCallout
color="violet-70" color="violet-70"
@ -73,7 +73,7 @@ After the applying these steps, you can update the configuration of your deploym
bold="Bare Metal Security" bold="Bare Metal Security"
href="/deployment/security/one-login/bare-metal" href="/deployment/security/one-login/bare-metal"
> >
Configure One Login SSO for your Bare Metal Deployment. Configure OneLogin SSO for your Bare Metal Deployment.
</InlineCallout> </InlineCallout>
<InlineCallout <InlineCallout
color="violet-70" color="violet-70"
@ -81,7 +81,7 @@ After the applying these steps, you can update the configuration of your deploym
bold="Kubernetes Security" bold="Kubernetes Security"
href="/deployment/security/one-login/kubernetes" href="/deployment/security/one-login/kubernetes"
> >
Configure One Login SSO for your Kubernetes Deployment. Configure OneLogin SSO for your Kubernetes Deployment.
</InlineCallout> </InlineCallout>
</InlineCalloutContainer> </InlineCalloutContainer>

2
openmetadata-docs/content/deployment/security/one-login/kubernetes.md
View File

@ -1,5 +1,5 @@
--- ---
title: One Login SSO for Kubernetes title: OneLogin SSO for Kubernetes
slug: /deployment/security/one-login/kubernetes slug: /deployment/security/one-login/kubernetes
--- ---