SSO assertion requirements

As the administrator, you need the elements and attributes listed in the following tables for SAML 2.0 SSO assertions returned to the Google Assertion Consumer Service (ACS) after the identity provider (IdP) has authenticated the user.

Guidance for attributes

If you've set up SSO via a third-party Identity provider and your IdP's SAML assertion includes an <AttributeStatement>, Google will store these attributes until the user's Google Account session expires. (Session length varies and is configurable by the administrator.) After the account session expires, attribute information is permanently deleted within a week.

As with custom attributes in Directory, assertion attributes shouldn't include sensitive personally identifiable information (PII), such as account credentials, government ID numbers, cardholder data, financial account data, healthcare information, or sensitive background information.

Recommended uses for assertion attributes would include:

  • User IDs for internal IT systems
  • Session-specific roles

You can only pass a maximum of 2kB of attribute data in your assertions. Assertions that exceed the maximum allowed size will be rejected altogether, and cause the sign-in to fail.

Supported character sets

The supported character set depends on whether you’re using SSO profiles or the legacy SSO profile:

  • Legacy SSO profile—Attribute values must be low-ASCII strings (Unicode/UTF-8 characters are not supported and will cause the sign-in to fail).
  • SSO profiles—Unicode/UTF-8 characters are supported.

Return assertions to the ACS

Was this helpful?

How can we improve it?
4745060234537024150
true
Search Help Center
true
true
true
true
true
73010
false
false
false
false
Search
Clear search
Close search
Main menu