Configure the PeopleSoft application

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

Tasks

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
    Label

    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: https://ps-external.example.com

    Protected Web Resource

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

    For example: http://ps-internal.example.com:8000 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 https://ps-external.example.com/psp/ps/.

    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

  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 the Edit icon to modify an entry in the table, or click the Delete icon 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 enter the Host Header value.
  5. Complete the following steps to add a host. Repeat these steps as required:
    1. Click Add protected web resource.
    2. Enter a fully qualified hostname:port combination, like for example, https://backendserver1.atko.com:7001.
    3. Enter a weight from 1 to 100. Enter 0 to specify that a host is disabled.
    4. Click Okay.
  6. Optional. Configure health checks. They 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 the settings as required.
      Field Value

      Default

      Path The URI path to the resource used in the health check. /
      Method The HTTP method used in the health check. Always GET
      Status code The HTTP status code used to determine health. 200
      Interval The interval between health checks in seconds. 10
      Request timeout The health check request timeout in seconds. 1
      Healthy threshold The number of requests that must succeed before a host is considered healthy. 3
      Unhealthy threshold The number of requests that must fail before a host is considered unhealthy. 3
    4. Click Save.

Configure certificates

  1. Expand the Certificates tab.
  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.
  5. Verify the login attribute:
    Data Source Field Type Name
    IDP

    login

    Header PSUSER
  6. Click Done.

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