Create the application in Access Gateway
During this task we will create the JD Edwards application, specify a certificate (if required) and then add the required redirect policy.
- Create application
- Configure the application
- [Optionally] Configure load balancing
- [Optionally] Configure certificates
- Configure policy
To create the application in Access Gateway:
- Sign in to the Access Gateway Admin UI console.
Click the Applications tab.
Click +Add to add a new application.
From the Application menu, select Oracle JD Edwards Enterprise One, and click Create.
- In the Essentials pane enter:
Field Value Label The name of the application,
For example: JD Edwards
Public Domain The external facing URL of the application.
For example: https://jde-external.example.com
Protected Web Resource The URL and port combination of the Oracle JD Edwards Implementation that is being protected.
For example: http://jde-internal.example.com:7005 See Configure load balancing
Post Login URL
Enter an appropriate target URL.
For example https://jde-external.example.com/jde/owhtml.
Post Login URL may contain other elements specific to the implementation.
Group The group containing users who can access the JD Edwards instance.
Available since Access Gateway version 2022.2.3
Okta recommends that whenever possible load balancers and Access Gateway as a load balancer be implemented.
See About Access Gateway load balancing.
- Expand the Protected Web Resource tab.
- Enable Load Balancing By Access Gateway.
The Protected Web Resource tab expands to include a table of hostnames and weights that represent the target load balancing instances. This table is initially empty.
- Select a URL scheme. All added protected web resources will inherit this scheme. HTTP and HTTPS schemes are supported.
- Optional. Enable and specify Host Header value.
- Repeat as required:
- Click Add protected web resource. An empty row is added to the table.
- Enter a fully qualified hostname:port combination. For example, https://backendserver1.atko.com:7001.
- Enter a weight between 1 and 100. Enter 0 to specify a disabled host.
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.
- Click Okay to add the new host.
- For existing hosts in the table, you can:
- Click edit () to modify an existing host.
- Click delete() to delete an existing host.
Optional. Configure health checks:
Health checks 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.
- Enable Load Balancer Health Check.
- Click Edit to modify health check settings.
- Modify settings as required.
Path URI to resource used in health check. / Method HTTP method used. Always GET Status code HTTP status code used to determine health. 200 Interval Interval between health checks in seconds. 10 Request timeout Health check request timeout in seconds. 1 Healthy threshold Number of successful requests before a host is considered healthy. 3 Unhealthy threshold Number of failed requests before a host is considered unhealthy. 3
- Click Save to save changes or click Cancel to exit without saving.
- Expand the Certificates tab.
By default, a wildcard self-signed certificate is created and assigned to the application when the application is initially created.
- Optional. Click Generate self-signed certificate. A self-signed certificate is created and automatically assigned to the application.
- 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.
Click Next. The Attributes pane appears.
For detailed information on the attribute options, see Application attributes .
- Confirm the IDP login attribute.
By default the JD Edwards application template login field as the JDE_SSO_UID header. Change the value of the header field if required. Add additional header fields required by the application.
While optional, Okta recommends that all applications include certificates.
Click Next. The Policies pane displays.
- On the root policy row, click the Edit icon.
- Expand the Advanced sub-tab.
- In the Custom configuration tab, enter a proxy redirect for the target JD Edwards application.
proxy_redirect http://jde-app.domain.tld:7005 https://$host:$server_port;
Click Not validated when complete.
If all values are entered correctly, the Not Validated button will change to Validated.
- Click Okay.
- Click Done.