Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Following the OAuth 2.0 standard, ModelOp Center requires the following Okta configurations for a successful integration:

  1. Custom scope

    1. modelop_client

  2. Applications

    1. gateway-service

    2. internal-client

    3. external-integration-client

    4. go-cli

Proposed
Application
ID

Application
Type

Client Secret Required

Grant Type

Scope

Redirect URIs

gateway-service

Web

✔

  • Authorization Code

  • Refresh Token

  • openid

  • profile

  • email

  • offline_access

Sign-in redirect URIs

  • <ModelOp Center URL>/login/oauth2/code/gateway-service

Sign-out redirect URIs

  • <ModelOp Center URL>

internal-client

✔

  • Client Credentials

  • modelop_client

external-integration-client

Native

  • Implicit

  • openid

  • profile

  • email

  • <ModelOp Center URL>/jupyterOauth2ImplicitGrant.html

  • <ModelOp Center URL>/modelOpWDC.html

  • https://oauth.powerbi.com/views/oauthredirect.html

go-cli

Native

✔

  • Resource Owner Password

  • Refresh Token

  • openid

  • profile

  • email

  • offline_access

ModelOp Center URL as a trusted origin

For users to be redirected to ModelOp Center after login, the ModelOp Center URL has to be added as a trusted origin by following these steps:

  1. Open the Okta console

  2. Click the following tabs in the given order:

    1. Security

    2. API

    3. Trusted Origins

    4. Add origin

      1. Origin name: ModelOp Center

      2. Origin URL: <ModelOp Center URL>

      3. Choose Type:

        1. Cross-Origin Resource Sharing (CORS)

        2. Redirect

Required User Attributes

  • Family name

  • Given name

  • User name

  • Email

  • Group(s)

Okta Guide

For instructions on how to create the custom modelop_client scope, please follow the Okta: How to guide.

  • No labels