Google Workspace Domain Field Is Empty During Auth0 Self Service SSO Connection Setup

When creating a new Google Workspace connection using Auth0 Self Service Single Sign-On (SSO), the Google Workspace Domain field does not display a pre-populated value in the support ticket URL. Auth0 intentionally leaves this field blank to allow the addition of any domain during the initial setup and to protect security configurations. Auth0 populates the domain field only when an administrator edits an existing connection to help identify the specific connection.

• Auth0
• Self Service Single Sign-On (SSO)
• Google Workspace Connections

During the initial setup of a Google Workspace connection, administrators can add any domain. For security reasons, Auth0 hides domains entered into the Domains-Based Discovery Pre-Verified Domains and Domains to be Verified fields. This design prevents unauthorized visibility into which domains bypass ownership verification and which require mandatory verification.

How do the domain verification fields operate in Auth0?

Review the following field descriptions to understand how Auth0 handles domain verification during the Self Service SSO setup process.

• Domains-Based Discovery Pre-Verified Domains: Adding domains to this field creates an allowlist for domains that do not require ownership verification via Domain Name System (DNS).
• Domains to be Verified: This field forces ownership verification for a chosen list of domains.

Why does the domain appear when editing an existing connection?

Auth0 lists the domain in the Google Workspace domains field when an administrator creates a ticket to edit an existing connection. This behavior identifies the specific connection undergoing modification, which assists administrators in managing multiple connections.