A login loop occurs when an administrator attempts to access the Okta Access Gateway (OAG) management console via Secure Shell (SSH) on new deployments without Dynamic Host Configuration Protocol (DHCP) configured. Resolve this issue, caused by the Syslog service failing to start without an assigned IP address, by using DHCP during deployment or installing an older OAG release. During the SSH login attempt, Okta redirects the administrator to the login prompt repeatedly and prevents access to the management console.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Access Gateway (OAG)
• Secure Shell (SSH)
• OAG releases prior to 2025.8

The Syslog service fails to start if the server lacks an assigned IP address. The management console requires the Syslog service to run for system logging. A recent change prevents the Syslog service from starting if the interface lacks an assigned IP address. Additionally, network requirements might restrict access to the management console over a private interface.

How is the login loop resolved during a new deployment?

Resolve the login loop by enabling DHCP during deployment and assigning a static IP address after the initial setup.

1. Use Dynamic Host Configuration Protocol (DHCP) during the initial deployment to assign an IP address.
2. Assign a static IP address to the server after completing the initial setup.

What is the alternative workaround if DHCP is unavailable?

Deploy an older Okta Access Gateway release, such as version 2024.9 or earlier, and upgrade the server after completing the initial setup. Contact Okta Support to obtain the download link for the older release.

How are network interface requirements managed?

If the issue persists while using DHCP, network requirements might restrict access to the management console over a private interface. Review the network interface configurations to ensure proper access.

Related References

• Manage network interfaces