Okta Access Gateway Release Notes

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 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). 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 Administer Behaviors
• Documentation added on administering Advanced Policies. For more information see Advanced 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 Okta Access Gateway Supported Technologies.
• Documentation added on supported sample applications. For more information see Application Types.

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 KerberosKerberos is a computer-network authentication protocol that works on the basis of tickets to allow nodes communicating over a non-secure network to prove their identity to one another in a secure manner. applications. See Add a Kerberos Application.
• Capacity planning guidance has been expanded and improved with respect to disk requirements. See the Capacity Planning and Sizing section in Prerequisites 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 SSOAn acronym for single sign-on. In a SSO system, a user logs in once to the system and can access multiple systems without being prompted to sign in for each one. Okta is a cloud-based SSO platform that allows users to enter one name and password to access multiple applications. Users can access all of their web applications, both behind the firewall and in the cloud, with a single sign in. Okta provides a seamless experience across PCs, laptops, tablets, and smartphones. AgentA software agent is a lightweight program that runs as a service outside of Okta. It is typically installed behind a firewall and allows Okta to tunnel communication between an on-premises service and Okta's cloud service. Okta employs several agent types: Active Directory, LDAP, RADIUS, RSA, Active Directory Password Sync, and IWA. For example, users can install multiple Active Directory agents to ensure that the integration is robust and highly available across geographic locations. errors.