diff --git a/openmetadata-docs/content/connectors/dashboard/quicksight/index.md b/openmetadata-docs/content/connectors/dashboard/quicksight/index.md index 56d8e7fde98..05ba6acb389 100644 --- a/openmetadata-docs/content/connectors/dashboard/quicksight/index.md +++ b/openmetadata-docs/content/connectors/dashboard/quicksight/index.md @@ -37,6 +37,20 @@ the following docs to connect using Airflow SDK or with the CLI. To deploy OpenMetadata, check the Deployment guides. +AWS Quicksight Permissions +To execute metadata extraction and usage workflow successfully the IAM User should have enough access to fetch required data. Following table describes the minimum required permissions + +| # | AWS Quicksight Permission | +| :---------- | :---------- | +| 1 | DescribeDashboard | +| 2 | ListAnalyses | +| 3 | ListDataSources | +| 4 | ListDashboards | +| 5 | DescribeAnalysis | +| 6 | DescribeDataSet | +| 7 | ListDataSets | +| 8 | DescribeDataSource | + To run the Ingestion via the UI you'll need to use the OpenMetadata Ingestion Container, which comes shipped with custom Airflow plugins to handle the workflow deployment. diff --git a/openmetadata-docs/content/connectors/database/athena/index.md b/openmetadata-docs/content/connectors/database/athena/index.md index ed0ca65211e..3e76543170e 100644 --- a/openmetadata-docs/content/connectors/database/athena/index.md +++ b/openmetadata-docs/content/connectors/database/athena/index.md @@ -9,7 +9,7 @@ slug: /connectors/database/athena | Stage | Metadata |Query Usage | Data Profiler | Data Quality | Lineage | DBT | Supported Versions | |:------:|:------:|:-----------:|:-------------:|:------------:|:-------:|:---:|:------------------:| -| PROD | ✅ | ❌ | ✅ | ✅ | Partially via Views | ✅ | -- | +| PROD | ✅ | ❌ | ✅ | ✅ | 1.0 ( upcoming release ) | ✅ | -- | @@ -17,7 +17,7 @@ slug: /connectors/database/athena | Lineage | Table-level | Column-level | |:------:|:-----------:|:-------------:| -| Partially via Views | ✅ | ✅ | +| 1.0 ( upcoming release ) | TBD | TBD | diff --git a/openmetadata-docs/content/deployment/security/okta/index.md b/openmetadata-docs/content/deployment/security/okta/index.md index 609e854fc5b..bd0bd25c21e 100644 --- a/openmetadata-docs/content/deployment/security/okta/index.md +++ b/openmetadata-docs/content/deployment/security/okta/index.md @@ -60,8 +60,9 @@ This document will explain how to create an Okta app and configure it for OAuth. - The app is now configured. app-is-configured -### Step 4: Add Authorization Server to get the Issuer URL (optional) -This step and the following ones are not mandatory. It is recommended to create a separate authorization server for different applications. The authorization server needs an endpoint, which'll be the Issuer URL. +### Step 4: Add Authorization Server to get the Issuer URL +#### New Authorization Server +It is recommended to create a separate authorization server for different applications. The authorization server needs an endpoint, which'll be the Issuer URL. - Click on **Security -> API** in the left navigation panel. click-security-api @@ -74,15 +75,23 @@ This step and the following ones are not mandatory. It is recommended to create add-auth-server-save-changes This will generate the Issuer URL. +#### Default Authorization Server ( not recommended ) +It is recommended to create a separate authorization server for different applications. The authorization server needs an endpoint, which'll be the Issuer URL. +- Click on **Security -> API** in the left navigation panel. +click-security-api -### Step 5: Change the Issuer URL from Dynamic to Okta URL (optional) +- From the **Authorization Servers** tab, click on **default** server. +default-server + + +### Step 5: Change the Issuer URL from Dynamic to Okta URL Once the Authorization Server has been added, navigate to Security >> API >> Authorization Servers and click on the authorization server created in the previous step. click-auth-server-from-prev-step The Issuer URL shows up as Dynamic by default. Change the Issuer URL to Okta URL and save the changes. change-issuer-url -### Step 6: Create a Default Scope (optional) +### Step 6: Create a Default Scope - To create a default scope from **Security -> API**, click on the required **Authorization Server**. click-req-auth-server @@ -93,7 +102,7 @@ The Issuer URL shows up as Dynamic by default. Change the Issuer URL to Okta URL - Set as a **Default Scope**. set-default-scope -## Step 7: Add New Access Policy and Rule (optional) +### Step 7: Add New Access Policy and Rule - From **Security -> API**, click on the required **Authorization Server** - Navigate to the **Access Policies Tab** - Click on **Add New Access Policy** @@ -107,7 +116,7 @@ The Issuer URL shows up as Dynamic by default. Change the Issuer URL to Okta URL - Click on **Create Rule** to save the changes. add-rule -### Step 8: Where to Find the Credentials (optional) +### Step 8: Where to Find the Credentials - Once the app is configured, the **Client ID** can be used. - You can also go to **Application -> Application** as in step 2. - You should be able to see your application in the list. diff --git a/openmetadata-docs/images/deployment/security/okta/default-server.png b/openmetadata-docs/images/deployment/security/okta/default-server.png new file mode 100644 index 00000000000..783fe10324f Binary files /dev/null and b/openmetadata-docs/images/deployment/security/okta/default-server.png differ