This article addresses session loss that occurs during sign-in when using a Custom Domain with the Google Social connection. The authentication fails because the user is redirected to the default tenant domain instead of the configured Custom Domain, which results in a lost session.

The user receives a message indicating a session issue:

You may have pressed the back button, refreshed during login, opened too many login dialogs, or there is some issue with cookies, since we couldn't find your session.

• Google Social Connection

• Custom Domain Enabled

• Sign In Using Google Social

The issue occurs when the Developer keys are used with the Google Social connection while a Custom Domain is active.

To resolve the session loss, the user must either configure the Google Social connection with Production keys or discontinue the use of the Custom Domain.

1. Use Production keys for the Google Social connection.

2. Disable the Custom Domain feature.