yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-07-19 07:17:38 +00:00
Code Issues Packages Projects Releases Wiki Activity
OpenMetadata/docs/install/enable-security/okta-sso/okta-server-creds.md
parthp2107 e2578d6be3
Added documentation changes done in 0.5.0 branch to main (#1168) 
* GitBook: [#177] Documentation Update - Airflow

* GitBook: [#195] Removing Cron from databaseServices

* GitBook: [#196] Added trino

* GitBook: [#197] removed cron from config

* GitBook: [#198] Added Redash Documentation

* GitBook: [#199] Added Bigquery Usage Documentation

* GitBook: [#200] Added page link for presto

* GitBook: [#201] Added Local Docker documentation

* GitBook: [#202] Added Documentation for Local Docker Setup

* GitBook: [#203] Added Git Command to clone Openmetadata in docs

* GitBook: [#207] links update

* GitBook: [#208] Updating Airflow Documentation

* GitBook: [#210] Adding Python installation package under Airflow Lineage config

* GitBook: [#211] Change the links to 0.5..0

* GitBook: [#213] Move buried connectors page up

* GitBook: [#214] Update to connectors page

* GitBook: [#215] Removed sub-categories

* GitBook: [#212] Adding Discovery tutorial

* GitBook: [#220] Updated steps to H2s.

* GitBook: [#230] Complex queries

* GitBook: [#231] Add lineage to feature overview

* GitBook: [#232] Make feature overview headers verbs instead of nouns

* GitBook: [#233] Add data reliability to features overview

* GitBook: [#234] Add complex data types to feature overview

* GitBook: [#235] Simplify and further distinguish discovery feature headers

* GitBook: [#236] Add data importance to feature overview

* GitBook: [#237] Break Connectors into its own section

* GitBook: [#238] Reorganize first section of docs.

* GitBook: [#239] Add connectors to feature overview

* GitBook: [#240] Organize layout of feature overview into feature categories as agreed with Harsha.

* GitBook: [#242] Make overview paragraph more descriptive.

* GitBook: [#243] Create a link to Connectors section from feature overview.

* GitBook: [#244] Add "discover data through association" to feature overview.

* GitBook: [#245] Update importance and owners gifs

* GitBook: [#246] Include a little more descriptive documentation for key features.

* GitBook: [#248] Small tweaks to intro paragraph.

* GitBook: [#249] Clean up data profiler paragraph.

* GitBook: [#250] Promote Complex Data Types to its own feature.

* GitBook: [#251] Update to advanced search

* GitBook: [#252] Update Roadmap

* GitBook: [#254] Remove old features page (text and screenshot based).

* GitBook: [#255] Remove references to removed page.

* GitBook: [#256] Add Descriptions and Tags section to feature overview.

* GitBook: [#257] Update title for "Know Your Data"

Co-authored-by: Ayush Shah <ayush.shah@deuexsolutions.com>
Co-authored-by: Suresh Srinivas <suresh@getcollate.io>
Co-authored-by: Shannon Bradshaw <shannon.bradshaw@arrikto.com>
Co-authored-by: OpenMetadata <github@harsha.io>
2021-11-13 09:33:20 -08:00

3.0 KiB
Raw Blame History

Create Server Credentials

This document is all about how to create an Okta app and configure it for oAuth. It will generate information that is required to perform the single-sign-on activity.

Step 1: Create an Okta Account

  • Go to Create Okta Account.
  • Provide the required input and click on Sign Up.
  • Else you can continue with Google or GitHub.

Step 2: Create the OIDC app integration.

  • Once done with signup/sign in you will be redirected to the getting started page of okta.

Alt text

  • Click Applications -> Applications available on the left side of the panel.

Alt text

  • Click on Create App Integration button.

Alt text

Step 3: Configuring the app

  • Once you click on Create App Integration button.
  • Select OIDC - OpenID Connect.

Alt text

  • Then select the Application type. Select Web Application.

Alt text

  • Once selected, click Next.
  • Select Refresh token, Implicit(Hybrid). Once selected Implicit option, select Allow ID token with implicit grant type. In Refresh token behavior. Select Use persistent token. Provide the necessary input and click Save.

  • The app is now configured.

Step 4: Where to find the credentials

  • Once the app is configured, now the Client Id and Client secret can be used.
  • You can also go to Application -> Application like in step 2.
  • You should be able to see your application in the list.

Alt text

  • Click on your application.
  • You will find your Client id, Client secret, and Okta domain.

  • To get your issuer and audience click on Sign On available on top of the form.

Alt text

Step 5: Adding the details in openmetadata-security.yaml

  • Once the Client Id, Client secret, issuer, and audience are generated.

    Add those details in the openmetadata-security.yaml file in the respective field.

Alt text