Fix #12461: Azure SSO Docs (#14963)

This commit is contained in:
Ayush Shah 2024-01-31 13:21:07 +05:30 committed by GitHub
parent 52d287af57
commit 53d4511c8d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
13 changed files with 1 additions and 25 deletions

View File

@ -7,8 +7,8 @@ currently being supported with security updates.
| Version | Supported |
| ------- | ------------------ |
| 1.2.x | :white_check_mark: |
| 1.1.x | :white_check_mark: |
| 1.0.x | :white_check_mark: |
## Reporting a Vulnerability

View File

@ -7,8 +7,6 @@ slug: /deployment/security/azure/bare-metal
Get the `Client Id` and `Tenant ID` from Azure Application configured in [Step 3](/deployment/security/azure#step-3-where-to-find-the-credentials).
Get the Azure Service Application `Client Id`, `Client Secret`, `Authority`, `Scopes` from the information collected in [Step 9](/deployment/security/azure#step-9-note-down-the-clientid-and-authority).
## Update conf/openmetadata.yaml
```yaml

View File

@ -11,8 +11,6 @@ To enable security for the Docker deployment, follow the next steps:
Get the `Client Id` and `Tenant ID` from Azure Application configured in [Step 3](/deployment/security/azure#step-3-where-to-find-the-credentials).
Get the Azure Service Application `Client Id`, `Client Secret`, `Authority`, `Scopes` from the information collected in [Step 9](/deployment/security/azure#step-9-note-down-the-clientid-and-authority).
Create an `openmetadata_azure.env` file and add the following contents as an example. Use the information
generated when setting up the account.

View File

@ -9,8 +9,6 @@ Check the Helm information [here](https://artifacthub.io/packages/search?repo=op
Get the `Client Id` and `Tenant ID` from Azure Application configured in [Step 3](/deployment/security/azure#step-3-where-to-find-the-credentials).
Get the Azure Service Application `Client Id`, `Client Secret`, `Authority`, `Scopes` from the information collected in [Step 9](/deployment/security/azure#step-9-note-down-the-clientid-and-authority).
See the snippet below for an example of where to place the values and update the authorizer configurations in the `values.yaml`.

View File

@ -7,8 +7,6 @@ slug: /deployment/security/azure/bare-metal
Get the `Client Id` and `Tenant ID` from Azure Application configured in [Step 3](/deployment/security/azure#step-3-where-to-find-the-credentials).
Get the Azure Service Application `Client Id`, `Client Secret`, `Authority`, `Scopes` from the information collected in [Step 9](/deployment/security/azure#step-9-note-down-the-clientid-and-authority).
## Update conf/openmetadata.yaml
```yaml

View File

@ -11,8 +11,6 @@ To enable security for the Docker deployment, follow the next steps:
Get the `Client Id` and `Tenant ID` from Azure Application configured in [Step 3](/deployment/security/azure#step-3-where-to-find-the-credentials).
Get the Azure Service Application `Client Id`, `Client Secret`, `Authority`, `Scopes` from the information collected in [Step 9](/deployment/security/azure#step-9-note-down-the-clientid-and-authority).
Create an `openmetadata_azure.env` file and add the following contents as an example. Use the information
generated when setting up the account.

View File

@ -9,8 +9,6 @@ Check the Helm information [here](https://artifacthub.io/packages/search?repo=op
Get the `Client Id` and `Tenant ID` from Azure Application configured in [Step 3](/deployment/security/azure#step-3-where-to-find-the-credentials).
Get the Azure Service Application `Client Id`, `Client Secret`, `Authority`, `Scopes` from the information collected in [Step 9](/deployment/security/azure#step-9-note-down-the-clientid-and-authority).
See the snippet below for an example of where to place the values and update the authorizer configurations in the `values.yaml`.
```yaml

View File

@ -7,8 +7,6 @@ slug: /deployment/security/azure/bare-metal
Get the `Client Id` and `Tenant ID` from Azure Application configured in [Step 3](/deployment/security/azure#step-3-where-to-find-the-credentials).
Get the Azure Service Application `Client Id`, `Client Secret`, `Authority`, `Scopes` from the information collected in [Step 9](/deployment/security/azure#step-9-note-down-the-clientid-and-authority).
## Update conf/openmetadata.yaml
```yaml

View File

@ -11,8 +11,6 @@ To enable security for the Docker deployment, follow the next steps:
Get the `Client Id` and `Tenant ID` from Azure Application configured in [Step 3](/deployment/security/azure#step-3-where-to-find-the-credentials).
Get the Azure Service Application `Client Id`, `Client Secret`, `Authority`, `Scopes` from the information collected in [Step 9](/deployment/security/azure#step-9-note-down-the-clientid-and-authority).
Create an `openmetadata_azure.env` file and add the following contents as an example. Use the information
generated when setting up the account.

View File

@ -9,8 +9,6 @@ Check the Helm information [here](https://artifacthub.io/packages/search?repo=op
Get the `Client Id` and `Tenant ID` from Azure Application configured in [Step 3](/deployment/security/azure#step-3-where-to-find-the-credentials).
Get the Azure Service Application `Client Id`, `Client Secret`, `Authority`, `Scopes` from the information collected in [Step 9](/deployment/security/azure#step-9-note-down-the-clientid-and-authority).
See the snippet below for an example of where to place the values and update the authorizer configurations in the `values.yaml`.
```yaml

View File

@ -7,8 +7,6 @@ slug: /deployment/security/azure/bare-metal
Get the `Client Id` and `Tenant ID` from Azure Application configured in [Step 3](/deployment/security/azure#step-3-where-to-find-the-credentials).
Get the Azure Service Application `Client Id`, `Client Secret`, `Authority`, `Scopes` from the information collected in [Step 9](/deployment/security/azure#step-9-note-down-the-clientid-and-authority).
## Update conf/openmetadata.yaml
```yaml

View File

@ -11,8 +11,6 @@ To enable security for the Docker deployment, follow the next steps:
Get the `Client Id` and `Tenant ID` from Azure Application configured in [Step 3](/deployment/security/azure#step-3-where-to-find-the-credentials).
Get the Azure Service Application `Client Id`, `Client Secret`, `Authority`, `Scopes` from the information collected in [Step 9](/deployment/security/azure#step-9-note-down-the-clientid-and-authority).
Create an `openmetadata_azure.env` file and add the following contents as an example. Use the information
generated when setting up the account.

View File

@ -9,8 +9,6 @@ Check the Helm information [here](https://artifacthub.io/packages/search?repo=op
Get the `Client Id` and `Tenant ID` from Azure Application configured in [Step 3](/deployment/security/azure#step-3-where-to-find-the-credentials).
Get the Azure Service Application `Client Id`, `Client Secret`, `Authority`, `Scopes` from the information collected in [Step 9](/deployment/security/azure#step-9-note-down-the-clientid-and-authority).
See the snippet below for an example of where to place the values and update the authorizer configurations in the `values.yaml`.
```yaml