docs/content/stable/yugabyte-cloud/managed-security/managed-authentication/federated-okta.md
Using federated authentication, you can use an enterprise IdP to manage access to your YugabyteDB Aeon account. After federated authentication is enabled, only Admin users can sign in using password authentication.
Currently, YugabyteDB Aeon supports IdPs exclusively using the OIDC (OpenID Connect) protocol.
<ul class="nav nav-tabs-alt nav-tabs-yb"> <li> <a href="../federated-entra/" class="nav-link"> Microsoft Entra </a> </li> <li> <a href="../federated-ping/" class="nav-link"> PingOne </a> </li> <li> <a href="../federated-okta/" class="nav-link active"> Okta </a> </li> <li> <a href="../federated-jump/" class="nav-link"> JumpCloud </a> </li> <li> <a href="../federated-custom/" class="nav-link"> Custom </a> </li> </ul>Before configuring federated authentication, be sure to allow pop-up requests from your IdP; the provider may need to confirm your identity in a new window.
Before enabling federated authentication in YugabyteDB Aeon, you must configure your IdP and obtain the necessary credentials.
To use Okta for your IdP, do the following:
Sign in to your Okta account and create an app integration.
This displays the New Web App Integration window.
Set the web app integration settings as follows.
https://yugabyte-cloud.okta.com/oauth2/v1/authorize/callback as redirect URI.Your application is added to the Applications page.
To configure Okta federated authentication in YugabyteDB Aeon, you need the following application properties:
For more information, refer to App integrations in the Okta Identity Engine documentation.
To configure federated authentication in YugabyteDB Aeon, do the following:
At this point, you will be redirected to sign in to your IdP to test the connection. If the test connection is successful, federated authentication is enabled.