Article DetailsDetailsHelp DetailsWhen enabling PrivateLink or Private Service Connect for Aura instances with Single Sign-On (SSO) configurations, it is crucial to update the redirect URI to ensure continued seamless authentication. Since you will use https://<dbid>.production-orch-xxxx.neo4j.io/browser connecting to your aura instance. You should also adjust your redirect URI to ensure consistency. Within your IDP's Aura application, you need to change the FQDN part of your redirect URI from <dbid>.databases.neo4j.io to <dbid>.production-orch-xxxx.neo4j.io.For Example: Original redirect URI: https://abcd1234.databases.neo4j.io/browser/?idp_id=okta&auth_flow_step=redirect_uriUpdated redirect URI: https://abcd1234.production-orch-0001.neo4j.io/browser/?idp_id=okta&auth_flow_step=redirect_uri Updating the redirect URI for Single Sign-On after enabling PrivateLink or Private Service Connect for your Aura instances is essential for maintaining a secure and seamless authentication experience. Following the provided steps will help ensure that SSO configurations align with the updated private connectivity settings. For any additional assistance or inquiries, please refer to the Aura documentation or contact Aura support team.InformationTitleUpdating Redirect URI with PrivateLink in Aura InstancesArticle Created Date3/15/2024, 10:56 PMURL Name24951920192019-Updating-Redirect-URI-with-PrivateLink-in-Aura-InstancesLast Modified Date3/18/2024, 11:27 AM