

Using Okta as an External IDP with OIDC¶

Follow the instructions below to connect Okta as a third-party Identity Provider to WSO2 API Manager.

Pre-requisites¶

Before you begin, make sure you do the following.

Create an account in https://developer.okta.com/
Download API Manager 3.2.0 distribution from https://wso2.com/api-management/
Unzip the distribution and open the deployment.toml file located in <API-M_HOME>/repository/conf/ directory. Add the following configuration.
```
[tenant_mgt]
enable_email_domain= true
```
You need to enable this because Okta uses the email as the username by default. To use the email as the username in WSO2 API Manager you have to enable it as it is not enabled by default. Once enabled, you can use your email or a normal username as your username.
Start the WSO2 API Manager server.

Step 1 - Configure Okta¶

Navigate to the Okta Admin Portal.
Click Applications and then click Add Application.
Select the type as web and use the following details.
Add a new attribute to the default user profile of Okta to represent the user role.
1. Navigate to Users -> Profile Editor.
2. Click Profile to edit the default profile.
  
  You will be able to see the user attributes in the Profile Editor.
3. Click Add Attribute to add new user attributes.
4. Enter the user role details and click Save.
Add the claims that need to be returned from the ID Token in Okta.

These claims will be used to map the user details with WSO2 API Manager.
1. Navigate to API -> Authorization Servers and select the default server.
2. Add the following two claims as shown in the images below.
Enable WSO2 API Manager to map an internal role to a provisioned user.
1. Go to Users -> People and click on your profile name.
2. Navigate to the profile edit page as shown below.
3. Add any as the role value as shown below.
  
  This will be used by API Manager to map an internal role to a provisioned user.

Step 2 - Configure API Manager¶

Sign in to the WSO2 API-M Management Console.

https://localhost:9443/carbon.
Create a role that needs to be assigned to users that will be provisioned from Okta.
1. Go to Users and Roles.
2. Click Add to add a new role.
3. Assign the following permissions to the role and click Save.
Add role permissions via the WSO2 API Manager Admin Portal.
1. Sign in to the WSO2 API Manager Admin Portal.
  
  https://localhost:9443/admin
2. Click Settings and then click Role Permissions.
3. Click Add role permission.
4. Enter okta_role in the Provide role name field and click Next.
5. Go to Select permissions, click Custom permissions, and start assigning the permissions as shown below.
  
  These permissions will allow a user having the okta_role to login to Publisher and Developer Portals.
6. Click Save to save your changes.
Note

If you want your user to perform analytics-based tasks, you should add the okta_role to the required analytics scopes according to your preference. The steps below are given as an example.
1. Sign in to the API-M Management Console. https://localhost:9443/carbon
2. Navigate to Main > Resources > Browse.
3. Enter /_system/config/apimgt/applicationdata/tenant-conf.json as the location and click Go to browse the registry and locate the required resource.
4. Update the RESTAPIScopes JSON field by adding okta_role to the Roles field under the corresponding Name fields as shown below for the analytics related scopes.
```
{
    "Name": "apim_analytics:api_analytics:view",
    "Roles": "admin,Internal/creator,Internal/publisher,okta_role"
},
{
    "Name": "apim_analytics:application_analytics:view",
    "Roles": "admin,Internal/subscriber,okta_role"
},
```
5. Click Save Content.

Add an Identity Provider.

Sign in to the WSO2 API-M Management Console.

https://localhost:9443/carbon.
Click Main and then click Add under Identity Providers.
Enter the Identity Provider's Name.

Expand Federated authenticators -> OAuth2/OpenID Connect Configuration and add the following details.

Field		Sample value
Enable OAuth2/OpenIDConnect		True
Client id		You can find this value from the Okta application that you created.
Client secret		You can find this value from the Okta application that you created.
Authorization Endpoint URL		https://your_okta_url/oauth2/default/v1/authorize
Token Endpoint URL		https://your_okta_url/oauth2/default/v1/token
callback url		https://localhost:9443/commonauth
Userinfo Endpoint URL		https://your_okta_url/oauth2/default/v1/userinfo
Logout Endpoint URL		https://your_okta_url/oauth2/default/v1/logout
Additional Query Parameters		scope=openid%20profile

Expand Claim Configuration -> Basic Claim Configuration. Add the claim configurations as shown in the image below.
Expand Role configuration and add okta_role as shown below.

You can check if the user logged in has the role any and assign the local okta_role.
Enable Just-in-Time Provisioning for the user to be saved in the API Manager user store.

Info

When Just-In-Time Provisioning is enabled, the user details will be saved in the API Manager user store. User profile details will be updated via the federation following each login event. To preserve the user profile details without any changes you need to enable SystemRolesRetainedProvisionHandler.

Add the following to the <API-M_HOME>/repository/conf/deployment.toml file and restart the server.

[authentication.framework.extensions]
provisioning_handler = "org.wso2.carbon.identity.application.authentication.framework.handler.provisioning.impl.SystemRolesRetainedProvisionHandler"

Update the Service Providers.
1. Click Service Providers -> List in the WSO2 API-M Management Console.
  
  There are two service providers available by default; apim_publisher and apim_devportal.
2. Click Edit to edit apim_publisher.
  
  Warning
  
  You need to have signed in to the Developer Portal and Publisher at least once for the two service providers to appear, as it is created during the first sign in.
3. Expand Local & Outbound Authentication Configuration under Federated Authentication and select the identity provider you created.
4. Repeat the latter mentioned two steps for apim_devportal.

Now you will be able to Sign in to the Publisher and Developer Portal using Okta.

Top