Versions Compared

Version Old Version 18 New Version Current
Changes made by

Blagica

Miguel Rosas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

*When registering a new app, ensure you use the "App registrations" option under the “Applications” menu, and not the "Enterprise applications" option. Each option provides different settings, and selecting the wrong one will prevent you from completing the setup configuration successfully.

Proposed
Application Name

Platform Type

Client
Secret
Required

Scopes & API Permissions

App Roles & API Permissions

Token Claims

Redirect URIs

Token version

Other configurations

gateway-service
(C2B)

  1. Web

✔

  • custom_scope

  • family_name

  • given_name

  • preferred_username

  • email

  • groups

[Enable above claims for ID and Access_token]

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

2

internal-client
(B2B)

✔

  • Group.Read.All**

  • modelop_client

  • idtyp

external-integration-client
(C2B)

  1. Single-page application

  2. Mobile and desktop applications

  • custom_scope

  • family_name

  • given_name

  • preferred_username

  • email

  • groups

  1. Single-page application; Redirect URIs

    1. https://<ModelOp Center URL>/jupyterOauth2ImplicitGrant.html

    2. https://<ModelOp Center URL>/modelOpWDC.html

  2. Mobile and desktop applications; Redirect URIs

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

go-cli
(C2B)

✔

  • custom_scope

  • family_name

  • given_name

  • preferred_username

  • email

  • groups

...

2

The Group.Read.All permission for Microsoft Graph is necessary only if a customer is unable to include the group names, instead of group ids, as part of the access token. With Group.Read.All permission granted, ModelOp Center will be able to retrieve the group names from Microsoft Graph and display them instead of their ids throughout the platform. For details on how to grant permission Group.Read.All, please refer to Microsoft Entra ID: How-to guide.

...

Once the internal-client app has been created, please open the “Overview” tab for the app and click on:

  • "

...

  • Application ID URI "

...

“Set”

  • ( Top center ) - Click “Add”

  • “Save” the suggested Application ID URI.

external-integration-client
(C2B)

  1. Single-page application

  2. Mobile and desktop applications

  • custom_scope

  • family_name

  • given_name

  • preferred_username

  • email

  • groups

  1. Single-page application; Redirect URIs

    1. https://<ModelOp Center URL>/jupyterOauth2ImplicitGrant.html

    2. https://<ModelOp Center URL>/modelOpWDC.html

  2. Mobile and desktop applications; Redirect URIs

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

2

Please open the “Authentication” tab. Under “Implicit grant and hybrid flows”, please select:

✅ Access tokens (used for implicit flows)

✅ ID tokens (used for implicit and hybrid flows)

as the types of tokens that will be issued by the authorization endpoint for this particular app.

go-cli
(C2B)

✔

  • custom_scope

  • family_name

  • given_name

  • preferred_username

  • email

  • groups

2

Microsoft Entra ID Guide

For instructions on how to create custom_scopeand modelop_client, and how to set the access token version, please follow the Microsoft Entra ID: How-to guide.