Okta Access Gateway Release Notes

Fixes

• OKTA-283885 - In some situations, the Network Connectivity Test in the command console would fail with an invalid host name error for valid hosts.
• OKTA-290632 - Access Gateway didn't honor the maximum session duration setting. Some sessions were still valid after the maximum session duration was exceeded.
• OKTA-291181 - When there was no user session and the behavior Force reauthentication at IdP was enabled, reauthentication didn't occur as expected.

• Forwarding log events to syslog systems, such as Graylog, is now available.
  For more information see Administering Log Forwarding.
• Administrators can now download all Access Gateway log files.
  For more information see Download logs, and About Access Gateway logs.

Enhancements

• Documentation added for Oracle Application Express applications.
• Documentation added for Oracle Forms applications.
• Documentation added for Oracle WebCenter applications.

Fixes

• OKTA-275433 - When importing attributes in datastore’s, commas were inserted at the start and end of the attribute list. Removing the commas resulted in a partial list.

Enhancements

• Documentation added for Oracle Access Gate application.
• Documentation added for Oracle WebLogic application.
• Documentation added for Okta Access Gateway One Day Admin tutorial.
  
  

Fixes

• OKTA-275362- When modifying the field list in an existing LDAP datastore, removing all fields resulted in a field list with a single non-editable field with a blank name.
• OKTA-278510 - When initially accessing the Access Gateway command line console, the string "Repodata is over N weeks old. Install yum-cron? Or run yum makecache fast." was inadvertently displayed.
• OKTA-280578 - After upgrading from Access Gateway version 2020.01.0 or earlier, configuring high availability through the command line console caused the console to stop responding.
• OKTA-280615 - After upgrading from Access Gateway version 2020.1.0 or earlier, when attempting to place an application in maintenance mode, the Admin Console would redirect to the application page rather than the maintenance page.

Features

• High Availability is now available.

Enhancements

• Documentation updates for Adding Kerberos Applications and Adding Oracle PeopleSoft Applications.
• Documentation added for Adding Oracle JD Edwards Applications.
• Documentation added for Configuring High Availability.
• Documentation added for Access Gateway One Day Administration.
• Documentation added for Add an Oracle WebLogic Server Application.

Fixes

• OKTA-257420 - When the system time was updated through the Okta Access Gateway command line console, the User-Defined Cookie Domain value and Access Gateway Hostname values were reset.
• OKTA-274930 - The Unbound networking service log events weren't being captured to the syslog.
• OKTA-274975 - When using the Admin Console to create or update EBS applications in high availability clusters, the changes weren't propagated to worker nodes.
• OKTA-275416 - When performing updates on worker nodes in high availability clusters, the bootstrap process produced an invalid configuration causing the node not to start.
• OKTA-275757 - The Okta Access Gateway update process deleted the high availability configuration file on admin nodes.
• OKTA-276986 - When using the Admin Console to configure datastore definitions in high availability clusters, definitions with names that contain spaces weren't synchronized with worker nodes.

Features

• Documentation is enhanced for examples applications.

Enhancements

• Documentation added on administering Application Behaviors. For more information see About application behaviors
• Documentation added on administering Advanced Policies. For more information see Advanced Access Gateway Policy.
• Documentation added on administering the support VPN. For more information see Access Gateway Support VPN.
• Documentation added for all currently supported application versions. For more information see Supported technologies.
• Documentation added on supported sample applications. For more information see Access Gateway Supported Applications.

Fixes

• OKTA-252228 - When setting the system time via the management console (Services > NTP > Set system time), the current date and time was not displayed.
• OKTA-252305 - When escaping from either of the NTP entry menus the user was returned to the Services menu rather than the NTP menu.
• OKTA-258911 - When changing session cache, the fixed MB example shows 100MB for the 1000MB example. For more information see the Command Line Console > Services menu.
• OKTA-262774 - When resetting the system using the management console (System> Reset) Okta Access Gateway as incorrectly identified as SPGateway. 
• OKTA-269513 - When configuring NIC bonding using the management console (Networking >Setup NIC bonding)
  "Error command not found" was displayed and the command failed.

Features

• Access Gateway has been hardened around certain vulnerability issues.
• Documentation is enhanced for applications, and capacity planning.

Enhancements

• Documentation added to include how to add Kerberos applications. See Add a Kerberos App.
• Capacity planning guidance has been expanded and improved with respect to disk requirements.
  See the Capacity Planning and Sizing section inPrerequisites for deploying Access Gateway for more information.
• New documentation has been added on use of the Support VPN. See Access Gateway Support VPN for more information.

Fixes

• OKTA-258541 - Okta Access Gateway upgrades incorrectly prompted for passwords via sudo.
• OKTA-257725 - Okta Access Gateway upgrades failed with EBS SSO Agent errors.