Add an Oracle Access Gate Application


The purpose of this tutorial is to walk through the process of setting up an Oracle Access Gate application 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.

Access Gate Architecture



Create the Application in Access Gateway

  1. Navigate to your Access Gateway InstanceAn instance, or computer instance, is a virtual machine (VM) or individual physical computer, used to host a software appliance..

  2. In the Access Gateway Admin UI, sign in as an administrator.

  3. Click the Applications tab.

    Select applications tab

  4. Click +Add to add a new application.

    Click Add.

  5. Select the Oracle WebLogic option from the left column menu, and click Create.

    Select header based and click create.

    The New Protected Application wizard will start and display the Essentials pane for the application being added.

  6. In the Essentials pane specify the following:

    Field Value
    Label A name for the application.
    Public Domain A fully qualified host name such as <yourexteralname>.<your 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).>.
    In the example provided this would be
    Protected Web Resource

    The URL of the internal, protected, application.
    In the example provided this would be<port>/<path>

    • port - the port Oracle Access Gate is listening on for http requests.
    • path - represents the path to the application.
    Group Enter the group containing the users who should have access to the application.

    Post Login URL

    Enter or modify the post login URL. By default this field is enabled and contains value:

    Description [optional] An appropriate description for your application.
  7. Click Next.
    The Applications pane appears.
  8. The Applications page provides a list settings particular to Oracle Access Gate.
    Confirm the following fields and click Validate.
    Click Next when complete.
    OID DatasourceEnabled.  For more information on data sources seeAdminister DataStores
    OID HostFully qualified host name of the OID Host.
    OID PortThe port used to connect to the OID host.
    Defaults 3060.
    Bind UserThe user use for OID access.
    Defaults cn=oracleuser.
    Bind User PasswordPassword for Bind User.
    BaseUser search base
    Default cn=Users,dc=domain,dc=com

    User Search Attribute

    Attribute to search OID using.
    Default CN.

    Matching Attribute

    Attribute used for matching in the attributes step.
    Default: USER_NAME.

  9. The Attributes page provides a list of attributes that will be passed into the application as header fields.







    Use the pencil icon icon to edit the name and other values associated with this attribute as required.
    Add or modify any required attributes, and click Next.
    For more information on the attribute options, see Application Attributes.
    The Policies pane appears.

  10. Leave all policies unchanged and click Done.
    For more information on Application policies see Application Policy Overview and Administration User Policy Guide.

Test the Application

The following steps assign the application to a test account and then execute the application to verify basic functionality.

Assign the application

  1. Login to your Okta tenant as administrator.

  2. Select Application > Applications.

  3. Click the name of the newly added header application.

  4. Select the Assignments tab.

  5. Select Assign > Assign To People.

  6. Select an appropriate user and click Assign.



    Testing is typically initially done using the same user who is associated with administering Access Gateway

  7. Click Done.

Next Steps