Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update external-idp-okta.md #339

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update external-idp-okta.md #339

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
58 changes: 21 additions & 37 deletions ...ng-the-applications-lifecycle/manage-it-teams/external-idp/external-idp-okta.md
View file
Open in desktop
Expand Up @@ -15,7 +15,7 @@ To configure Okta authentication, follow these steps:

1. [Create an application in the Okta portal for the OutSystems Development Tool (Service Studio and Integration Studio)](#create-an-application-in-the-okta-portal-for-the-outsystems-development-tools-service-studio-and-integration-studio)

1. [Activate Okta configuration](#activate-okta-configuration)
1. [Configure Okta as OutSystems' Identity Provider](#configure-okta-as-outsystems-identity-provider)

## Create an application in the Okta portal for the OutSystems Consoles

Expand Down Expand Up @@ -121,54 +121,38 @@ To configure Okta authentication, follow these steps:

![Copy Client Id](images/client-id-ok.png)

## Activate Okta configuration
## Configure Okta as OutSystems' Identity Provider

To finalize and activate the Okta configuration for both Consoles and Development Tools, follow these steps:

1. Go to **Security** > **API**, and from the default **Authorization Servers** tab, click your authorization server name.

The server settings are displayed.

![URI metadata](images/metadata-ok.png)

1. Copy the **Metadata URI** link.

**Note**: You need this information when configuring the provider in LifeTime.

1. To configure and activate the provider, follow the steps in the [LifeTime](#lifetime) section using the following details for for the OIDC provider information:

1. Click the **Use a different Client Ids for Desktop and Web tools** link and add both Application IDs using the following details:

* **Name**: Okta

* **OpenID Connect metadata document**: Metadata URI

* **Client Id for Web tools**: OutSystems Consoles Client ID

* **Client Secret**: OutSystems Consoles Client Secret

* **Client Id for Desktop tools**: OutSystems Development Tools Client ID












1. Access the Lifetime console.

1. Go to **User Management** > **Authentication Settings** and click **Add OpenId Connect Provider**.

1. Enter the following details according to the OIDC provider you are using:

1. **Name**: ID Provider (e.g., OKTA OIDC)

1. **Well-known Configuration URL**: OpenID Connect metadata document URI.

**Note** This URI can be found in OKTA's portal by navigating to **Security** > **API**, and from the default **Authorization Servers** tab, click your authorization server name.

![URI metadata](images/metadata-ok.png)

1. **Client ID Type**: Select the option **Different Client ID for Desktop and Web tools**.

1. **Client ID dor Desktop Tools**: Fill in with the ID of the application used in section [Create an application in the Okta portal for the OutSystems Development Tool (Service Studio and Integration Studio)](#create-an-application-in-the-okta-portal-for-the-outsystems-development-tools-service-studio-and-integration-studio)

1. **Client ID for Web Tools**: Fill in with the ID of the application used in section [Create an application in the Okta portal for the OutSystems Consoles](#create-an-application-in-the-okta-portal-for-the-outsystems-consoles)

1. **Username Claim**: The claim used to match the username field of the user configured in LifeTime which will need to be ``preferred_username`` for OKTA. For more information about claims, see [Standard Claims](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims).

1. Click **Save Changes**.

1. Before make Okta as the effective IdP, make sure to test the configuration and ensure that the Okta's users have a corresponding user created in the OutSystems platform first.

1. Click **Activate**.

1. In the pop-up window that will appear, fill in the **Client Secret** stored earlier.

1. Click the **Activate and Logout** button to start using Okta as the external Identity Provider of the OutSystems platform.