Configure the PeopleSoft application

During this task we will create the Oracle PeopleSoft application in Access Gateway.


Add the application

  1. Sign in to the Access Gateway Admin UI console.
  2. Click the Applications tab.
  3. Click +Add.
  4. Select Oracle PeopleSoft from the left column menu, and upper right-click Create.

Configure the application

  1. In the Essentials pane enter:

    Field Value

    The name of the application, as shown in your Okta tenant.

    For example: PeopleSoft SSO.

    Public Domain

    The customer facing URL of the PeopleSoft application.

    For example:

    <> must match the PeopleSoft domain, which is in the Protected Web Resource section as domain.tld.

    Protected Web Resource

    The URL and port combination of the Oracle PeopleSoft Implementation being protected.

    For example: See Configure load balancing.

    Post Login URL

    Browseable route-through location to pick up the required cookie from Okta Access Gateway and pass along to the Oracle PeopleSoft implementation.

    For example

    Note that the post login URL is automatically populated and can contain other elements specific to the implementation.

    Group The group containing users who can access the PeopleSoft instance.
  2. Expand Advanced section and click enable Content Rewrite.

Configure load balancing

Only use Access Gateway as the load balancer. See Load balancing.

  1. Expand the Protected Web Resource tab.
  2. Enable Load Balancing By Access Gateway.

    A table of hostnames and weights representing the target load balancing instances appears. This table is initially empty. Click edit to modify an entry in the table, or click delete to delete an entry.

  3. Choose either HTTP or HTTPS as the URL scheme. Each protected web resource that you add inherits this scheme.
  4. Optional. Enable and specify Host Header value.
  5. Complete the following steps to add a host, repeat as required:
    1. Click Add protected web resource.
    2. Enter a fully qualified hostname:port combination (for example,
    3. Enter a weight from 1 to 100. Enter 0 to specify that a host is disabled.

      Weights represent the percentage of requests that will be routed to this host.

      For example, two hosts of weights 2:1 would result in requests being routed ~66% to the host weighted 2 and ~33% to the host weighted 1.

    4. Click Okay.
  6. Optional. Configure health checks, which use GET operations to confirm that back-end resources are functional.

    New requests aren't routed to resources that have been labeled unhealthy by the health checks.

    1. Enable Load Balancer Health Check.
    2. Click Edit to modify health check settings.
    3. Modify settings as required.


      PathThe URI path to the resource used in health check./
      MethodThe HTTP method used.Always GET
      Status codeThe HTTP status code used to determine health.200
      IntervalThe interval between health checks in seconds.10
      Request timeoutThe health check request timeout in seconds.1
      Healthy thresholdThe number of requests that must succeed before a host is considered healthy.3
      Unhealthy thresholdThe number of requests that must fail before a host is considered unhealthy.3
    4. Click Save to save changes or click Cancel to exit without saving.

Configure certificates

    All apps, including the Access Gateway Admin UI console app, require a self-signed or signed certificate.

    Include signed certificates wherever you terminate SSL. You can terminate SSL at Access Gateway or any other network component, like a load balancer.

    If you terminate SSL at a load balancer, on the Access Gateway Admin UI console app, you also need to use a certificate that is trusted by the load balancer.

    If you terminate SSL on the Access Gateway Admin UI console application, you must use a signed certificate, which must be on the Access Gateway node and be associated with the Access Gateway Admin UI console application.

  1. Expand the Certificates tab.

    By default, when you create the app, the system generates a self-signed wildcard certificate and assigns it to the app.

  2. Optional. Click Generate self-signed certificate. A self-signed certificate is created and automatically assigned to the app.
  3. Optional. Select an existing certificate from the list. 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.
  4. Click Next. The Attributes pane appears. See Application attributes.

    The required attributes are pre-populated, and are presented for reference.

  5. Verify the login attribute:
    Data SourceFieldTypeName


    The attribute in your Okta tenant that stores the PeopleSoft username. This can be a different attribute or can use Okta username mapping to create the PeopleSoft username dynamically.

  6. Click Done.

The application is added and the Application list page is displayed.