Configure SAML access to your Okta Tenant
Accessing Access Gateway from your Okta tenant can be configured 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.. Once configured an administrator can log quick into Access Gateway using a tile.While not strictly required, its considered a best practice to configure access to the Access Gateway UI console from Okta. In this page walk thru the configuration of Access Gateway with an Okta tenant such that the Gateway 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. UI accepts a SAML token for Okta for authentication. We will also create an application tile on the Okta Applications page for administrator use to access the Gateway Administration UI.
Create a Token
In your browser, Navigate to your Okta OrgThe Okta container that represents a real-world organization. and Login as an Administrator.
Click Security > API.
Select the Tokens tab.
Click the Create Token.
Enter an appropriate name for the token. For example OAG Admin Access Token.
Note: All access to the Okta Access Gateway will be tracked using this token name.
Select and copy the token value.
Note: Token text is only available during creation. You will NOT be able to retrieve the text of the token at a later time.
Add Okta as IDP
In your browser, navigate to the Okta Access Gateway UI as Admin
Select the Identity Providers tab.
In the Identify Providers pane click the + icon and select Okta.
Select the Identity Providers tab.
Complete the Add New Okta IDPAn acronym for Identity Provider. It is a service that manages end user accounts analogous to user directories such as LDAP and Active Directory, and can send SAML responses to SPs to authenticate end users. Within this scenario, the IdP is Okta. step by providing the following values
Attribute Value Name A descriptive name Okta Org Your Okta Org URL. For example myorg.okta.com, Okta API Token API Token copied previously Description An appropriate description
Click Not Validated.
Note: If your token can be successfully validated then the yellow Not Validated button will become a green Validated button.
Configure SAML for Administrative access
In your browser, return to your Okta org as Administrator.
Click Add Group.
In the Add Group dialog name the group and add a description, then click Add Group.
Click the name of the newly added group.
Click Manage People and add all users who should be able to administer Okta Access Gateway.
When complete, click Save.
Return to the previously open Okta Access Gateway browser window.
Select the Application tab.
On the row representing the previously added idP, click Add.
From the list of applications select Access Gateway AdminUI and click Create.
In the Essentials section configure the following values and then click Next.
Attribute Value Label OAG Admin Console Public DomainA domain is an attribute of an Okta organization. Okta uses a fully-qualified domain name, meaning it always includes the top-level domain (.com, .eu, etc.), but does not include the protocol (https). gw-admin.<yourdomain> Groups OAG Admin (group created previously) Description An appropriate description
Click Next. The Attributes tab is displayed.
Click Next. The Policies tab is displayed.
Log out of the OAG Admin UI Console.
- Login to your Okta org as a user in the previously created OAG Admin group.
- You should see a notification has been added to the Okta Access Gateway Admin Console.
- Click the application tile and you will be logged into the Okta Access Gateway as an administrator.