Sample cookie application

The purpose of this tutorial is to walk through the process of setting up a sample cookie application through the Access Gateway Admin UI console.

Before you begin

Ensure that:

  • 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 an 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.
  • Appropriate DNS entries exist for the application.

Create sample cookie application

  1. Sign in to the Access Gateway Admin UI console.
  2. Click the Applications tab.

  3. Click +Add to add a new application.

  4. Select the Access Gateway Sample Cookie option from the left column menu, and click Create.

    Select add and the clicke Sample Cookie App.

    The New Protected Application wizard will start and display the Setting tab for the application being added.

  5. In the Essentials pane specify the following:

    Field Value
    Label A name for the application. Default is Sample Cookie App.
    Public Domain A fully qualified host name such as cookie.<your domain tld>
    Group Enter the group containing the users who should have access to the application.
    Description Optional. An appropriate description for your application.
  6. Important Note

    Important

    While optional, Okta recommends that all applications include certificates.
    See About Access Gateway Certificates for general information about certificate.
    See Certificate management tasks for a general task flow for obtaining and assigning certificates.  

  7. Expand the Certificates tab.
    Note

    Note

    By default a wild card self signed certificate is created and assigned to the application when the application is initially created.

  8. Optional. Click Generate self-signed certificate

    A self-signed certificate is created and automatically assigned to the application.
  9. Optional. Select an existing certificate from the list of provided certificates.
    Use the Search field to narrow the set of certificates by common name.
    Use the page forward (>)and backward(<) arrows to navigate through the list of available certificates.

[Optional]Add additional cookie attributes

  1. Click Next. The Attributes pane displays.
  2. In the Attributes pane, click the +.

    add-sample-header-app-okta.07

    The Add new Attribute window opens after the list of existing attributes.

  3. Populate the new attribute as follows:

    Field Description Example
    Data source Source of the attribute. One of IDP, Static, Secret, Auth Context or App Context
    See About application attribute data stores
    IDP
    Field Field name from the fields supported by the selected datasource.
    Note: Static and Secret fields are arbitrary text values.
    firstName
    Type The type of the attribute. Header or Cookie.
    Select Cookie to have the field added to the cookie header field. See about About application cookie headers fields for more information.
    Cookie.
    Name Unique name for the value in the cookie header fieldName

    See About application attribute elements for more details on attribute elements.

  4. Click Okay to add the new field, or Cancel to cancel.

    Repeat as required for additional attributes.

  5. Click Done.
    Access Gateway adds the new application and redirects to the Applications tab.

Test the sample cookie application

  1. Click Goto application and select IDP Initiated to verify the application is working.

    Test a sample cookie application

    Info

    Note

    Your Okta tenant administrator may need to assign the cookie application to you.

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

Note

Access Gateway inserts the cookie header into the request before it is sent to the back-end web application.

Related topics