Integrate with an Okta Tenant

 

Before applications can be secured, an Okta tenant must be configured to provide identity services.
Access Gateway and your Okta orgThe Okta container that represents a real-world organization. integrates using SAMLAn acronym for Security Assertion Markup Language, SAML is an XML-based standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP). The SAML standard addresses issues unique to the single sign-on (SSO) solution, and defines three roles: the end user, the IdP, and the SP. Here's how SAML works through Okta: SP-initiated flow: the end user requests (principally through a browser) a service from the SP. The SP requests and obtains an identity assertion from the IdP (in this case, Okta). On the basis of this assertion, the SP can decide whether or not to authorize or authenticate the service for the end user. IdP-initiated flow: with Okta as the IdP, an end user goes to the Okta browser and clicks on an app, sending a SAMLResponse to the configured SP. A session is established with the SP, and the end user is authenticated. and REST APIs.
The diagram below represents how your Okta tenant connects to Access Gateway using SAML.


To configure Access Gateway to integrate with an Okta org you must:

  1. Create an Okta Service Account for Access Gateway
  2. Create an Okta API Token
  3. Configure Okta as IDP in Access Gateway

Create an Okta Service Account for Access Gateway

  1. In your browser, Navigate to your Okta Org and sign in as an Administrator.

    Tip

    Best Practice

    Okta recommends creating a specific Service Account in Okta that will be used to create the Access Gateway API key. This is important because every action performed by an API key is logged under the user that created the key. In the interest of maintaining accurate logs, a dedicated Access Gateway Service Account is recommended.

  2. Navigate to the Directory > People section.
  3. Click Add Person.
  4. Enter a descriptive First name and Last name for the Service Account naming fields (i.e Service AdminAn abbreviation of administrator. This is the individual(s) who have access to the Okta Administrator Dashboard. They control the provisioning and deprovisioning of end users, the assigning of apps, the resetting of passwords, and the overall end user experience. Only administrators have the Administration button on the upper right side of the My Applications page.). Enter a dummy email
    (For example, service.admin@domain.com) for the Username and Primary email.
    Tip

    Best Practice

    Use a dummy value for the Username and Primary email fields so that there is not interference between the Service Account and your own account in the event of a password reset request, etc. Adding your own email address to the Secondary email field ensures you can activate and maintain the Service Account.

  5. Enter your valid Administrator Email in the Secondary email field. Click the Send user activation email checkbox, and click Save.
  6. You should now see your newly created Service Account under the Activated people tab with a Password reset status.
  7. Navigate to the Security > Administrators section.
  8. Click Add Administrator.
  9. Enter the name of the Service Account created earlier in the Grant administrator role to field. . Click the Super Administrator checkbox, and click Add Administrator.
  10. You should now have two Super Administrator accounts.
  11. Sign out of your Okta Admin Account.
  12. In your email, open the Service Account Activation Email you received from Okta and click the Activation link.
  13. After clicking the link, you will be asked to create a password, answer a security question, and select an account security image.
  14. Upon completion, log in with the new Service Account credentials.

Create an Okta API Token

  1. In the Service Account Dashboard, select Security > API from the menu options.

  2. On the API page, click Create Token.

  3. Enter a Token Name in the pop-up window, and click Create Token.

    Best Practice: Use a name that easily identifies the token’s purpose. In this case, the token is being used in an Access Gateway appliance, so including "Access Gateway" or "OAG" and other relevant information is recommended

  4. Copy the displayed Token Value in a safe place before clicking Ok, got it
  5. Warning: Once you close the pop-up window, you can never display the token value again! Please ensure you copy the token to a safe, secure location (such as a password manager or secure note database) for future reference.

Configure Okta as IDP in Access Gateway

  1. In your browser, navigate to the Access Gateway Admin UI and login as an administrator.
  2. Select the Settings tab.
  3. Click the Identity Providers pane.
  4. Click the + button, and Select OKTA.
  5. Enter an appAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in. name in the Name field, fill out the Okta Org URL and Okta API Token fields with the value generated earlier, and click Not Validated.configure-idp-okta.08.png
  6. Once the Okta API Token is validated, the Not Validated button will turn green and change to [Validated]
  7. Click Okay.
  8. The Settings tab will now display your Okta IDP status; verify it displays a Valid status.
    configure-idp-okta.09.png
  9. Navigate to the Topology tab to test the IDP’s connection.
  10. Click the Okta IDP icon to be redirected to your Okta tenant.

    configure-idp-okta.10.png
Top