Using Okta as an External IDP with SAML

Follow the instructions below to connect Okta as a third party Identity Provider to MWARE ESB.

Prerequisites

Before you begin, make sure you do the following.

  1. Create an account in https://developer.okta.com/
  2. Download MWARE ESB 4.1.0 distribution from https://wso2.com/api-management/
  3. Unzip the distribution and open the deployment.toml file located in <APIM_HOME>/repository/conf/. 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 MWARE ESB 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.
  4. Start the MWARE ESB server.

Step 1 - Configure Okta

  1. Login to the Okta developer console and switch to the classic UI.

  2. Go to Applications -> Add Application. Add new Okta SAML application

  3. Click Create New Application. Create new Okta SAML application

  4. Select Web as the Platform. Select SAML 2.0 as the sign-on method. Create a new application integration

  5. Enter the General Settings as shown in the images below. Enter application name

    Enter application details

    Warning

    Audience URI should be same as the Identity Provider entity id name that is created in MWARE ESB.

  6. Inside the SAML app you created go to Sign On and click View Setup Instructions.

    View Setup Instructions

    1. Scroll up to the Provide the following IDP metadata to your SP provider section. Copy and save the details given to a XML file.

      Copy and save xml

    2. Go to Assignments -> Assign. Click Assign to People and assign your current user.

      Assign your current user

  7. Switch back to the Developer Console shown in step 1.

  8. Follow these steps to add a new attribute to the default user profile of Okta to represent the user role.

    1. Navigate to Users -> Profile Editor and click the pencil icon to edit the default profile.

      Edit the default profile in the Profile Editor

    2. Click Add Attribute to add new user attributes.

      Add new attribute

  9. Enter the user attributes shown in the image below. Click Save.

    Add new attributes

  10. Follow the steps below to edit the user profile.

    1. Go to Users -> People and click on your profile name.

    2. Click Edit to change the profile details.

    3. Add the Role. This will be used in the ESB to map an internal role to the provisioned user.

Step 2 - Setup API-Manager

  1. Log in in to https://localhost:9443/carbon.

  2. Create a role that needs to be assigned to users that will be provisioned from Okta.

    1. Go to Users and Roles.

    2. Add a new role.

    3. Assign the following permissions to the role and save the role.





  3. Log in to https://localhost:9443/admin.

    1. Expand Settings and click Scope Mapping.

    2. Update the following scopes with the okta_role.





      These permissions will allow a user having the okta_role to log in to Publisher and Developer Portals.

  4. Add an Identity Provider.

    1. Sign in to the MWARE ESB Management Console. https://localhost:9443/carbon

    2. Click Main and then click Add under Identity Providers.

    3. Enter the Identity Provider's Name.



    4. Expand Federated authenticators -> SAML2 Web SSO Configuration section. Under Select Mode, select Metadata File Configuration. Update the XML file obtained during the Okta setup process Step 1 - 6(a).

    Field Sample value
    Specifies if SAML2 Web SSO is enabled for this Identity Provider True
    Service Provider Entity ID Entity ID specified when creating SAML app (e.g., oktasaml)

  5. Expand Claim Configuration -> Basic Claim Configuration. Add the claim configurations as shown in the image below. The role drop-down menu contains the roles you configured in Okta (Step 1). Select the Identity Provider Claim URIs according to the configurations in the Okta Developer Console in Step 1.

  6. 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.

  7. Enable Just-in-Time Provisioning for the user to be saved in the ESB user store.

  8. Select a Service Provider.

    1. Navigate to Service Providers -> List.

    2. There are two service providers created apim_publisher and apim_devportal. Click Edit for 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. Select Federated Authentication and select the name of the Identity Provider you created from the corresponding drop-down menu.

    Repeat this step for apim_devportal as a Service Provider.

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

Top