Add a Sample Header Application through Okta

The purpose of this tutorial is to walk through the process of setting up a sample header application with Okta through the Access 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. Console.

Create the Application in Access Gateway

1. Navigate to your selected https://gw-admin.gateway.info page to access the Access Gateway Instance.

   Note: Access Gateway creates a default self-signed certificate. For non-production deployments, this will be appropriate. Proceed past any security exceptions raised by your browser. For production deployments, a valid certificate can be installed and these exceptions will not be needed.

2. In the Access Gateway Admin Console, enter your login credentials and click Login.

   Username: admin
   Password: <default password>
   

3. Click the Applications tab.

   

4. Click +Add to add a new application.

   

5. Select the Access Gateway Sample Header 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. option from the left column menu, and click Create.

   

    

Configure the Header Application Settings

1. Click Next.

   Note: The Settings page provides options with which to further configure the application. For more information on the application setting options, see Application Settings .

Configure the Header Application Attributes

1. Click Next.

   Note:The Attributes page provides a list of attributes that will be passed into the application. This page also provides the ability to add, edit, or remove any attribute. For more information on the attribute options, see Application Attributes .

Add a Custom Attribute to Okta

1. In a new tab, Navigate to your Okta OrgThe Okta container that represents a real-world organization. and log in as an Administrator.

2. Navigate to the Directory > Profile Editor section.

   

3. Click Profile in the Actions column.
4. Click + Add Attribute to add a custom attribute that will be used to send header information through the Sample Header Application.
5. Enter Gender for the Display name and gender for the Variable name. Click Save.
6. Click Directory → People.
7. Select your account under the Person & Username column.
8. Click the Profile tab, and click Edit.
9. Scroll down to the Gender attribute, and enter a corresponding value.
10. Click Save.

Complete the Header Application Configuration

1. Return to the Access Gateway Admin Console.

2. Select the new application and click the pencil icon.

   

3. In the Attributes section, click the +.

   

4. Scroll down to the Add new Session Attribute window.

5. In the Name field, enter manager, and select the manager attribute type in the Value field.

6. Click Okay.

   

   Note: In the Value menu, type in the name of the attribute you want to add, and then click the new attribute in the dropdown menu.

7. Click Next.
8. Click Done.
9. Confirm that the Sample Header App is displayed as Active in the Protected Applications list. . Click the Goto App icon.

   Important: Ensure that the 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). defined in the Configure the Header Application Settings is added to local host file or DNS Server pointing to the VM running Access Gateway.

   <ip address>     <app public domain>
   xxx.xxx.xxx.xxx  header.gateway.info
   

Test the Sample Header Application

1. Select 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. Initiated from the drop down menu to verify the application is working.

   

   Note: If you do not already have an active session for Okta open in your browser, you may be prompted to log in to your Okta account and provide your credentials.

2. In the application page, review and verify that the Sample Header App sent to Okta matches your profile information.