Add a no-auth app to Access Gateway
The purpose of this tutorial is to walk through the process of setting up a no-auth application through the Access Gateway Admin Console.
- Access Gateway is installed and configured for use.
See Manage Access Gateway deployment.
- Access Gateway has been configured to use your Okta tenant as IDP.
See Configure your Okta tenant as Identity Provider for more information about configuring your Okta tenant as an IDP.
- You have administrator rights on your Okta tenant and can assign applications to users, and create groups.
- Navigate to your Access Gateway Instance and sign in as admin.
- Click the Applications tab
- Click + Add to add a new application.
Select the No-auth application type from the list available in the left section of the page, and click Create.
The New Protected Application wizard will start and display the Setting tab for the application being added.
- The Settings page provides options with which to configure the
application. Review the options and make the appropriate changes.
For more information on the application settings options, seeAbout application settings
- Enter the following values in their respective fields, and click
Field Value Public Domain noauth.okta.com Protected Web Resource https://header.service.gateway Post Login URL https://noauth.okta.com Groups Select IDP group that should be able to access this application.
- Review the Essentials page and then click Next.
The Attributes pane appears.
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.
Add any required attributes, and click Next.
For more information on the attribute options, see Application attributes
The Policies pane appears.
The Policies pane provides a list of protection policies (if any exist) for the application.
Leave all policies unchanged and click Done.
For more information on Application policies see About application policy and Manage application policy .
Make sure that the public domain defined in Essential section is added to the local hosts file pointing to the machine that hosts Access Gateway. For example, the application in this example has been created using the public domain:
header.service.gateway. In order to access this, you must add
xxx.xxx.xxx.xxx noauth.okta.comto the local hosts file where
xxx.xxx.xxx.xxxis the IP address of the machine that hosts Access Gateway.
When testing, note that the address bar changes the Header Local URL to the Public Domain URL (in this example, https://noauth-okta.com).
The following steps assign the application to a test account and then execute the application to verify basic functionality.
Assign the application
Login to your Okta tenant as administrator.
Select Application > Applications.
Click the name of the newly added header application.
Select the Assignments tab.
Select .Assign > Assign To People.
Select an appropriate user and click Assign.
Testing is typically initially done using the same user who is associated with administering Access Gateway
Execute the Application
Return to the Access Gateway admin console.
On the row representing the newly added no-auth app, select Goto application > SP Initiated.
- Verify the results page displays all expected attribute values.
- Close the results page.
On the Results page, review and verify that No-auth App sent the expected profile information.
If the application is configured properly, you will be able to access this Protected Web Resource via the Public Domain address configured in the Access Gateway App.
- For information about the generic header application please see Add a generic header application.
- For information about the sample header application please see Add a sample header application.
- For information on the sample policy application please see Add a sample policy application.
- Add or review application essential settings. For more details see About application essentials and Manage application essentials.
- Add application behaviors. For details and examples of behaviors see About application behaviors.
- Add fine grained policy to further protect resources. An overview of user policy can be found in About application policy.
For details and examples of policy see Manage application policy .
- Extend existing policy using Custom configuration, see Advanced Access Gateway Policy.
- Define one or more certificates for use with this application. See Configure certificates.
- Add supplemental database or LDAP based data stores. For more information see Administer data stores.