Do you use Google SAML authentication in place of Stanford single-sign-on (SSO) to verify your identity when logging into various services? Do you support users with personal Gmail accounts connected to a SUNet ID alias? If so, this message is for you.
What’s changing?
Although many Stanford users have opted to generate preferred names and email aliases, this information isn’t always linked back to their Google accounts. An update is coming March 16 at 9 a.m. to sync the Stanford person registry with Stanford’s Google Suite and Google Cloud Platform (GCP).
What’s the impact?
Those IT groups who rely on Google SAML authentication instead of Stanford SSO for applications in the cloud may experience login issues after this change. Additionally, Stanford users who have signed up for personal Google accounts using their SUNet ID as an alias may be prompted by Google to remove that alias from their personal account.
The use of Google SAML authentication is not recommended or supported by Stanford’s Information Security Office.
Get help
If you need help getting started with Stanford SSO, call the IT Service Help Desk at 650-725-4357 (5-HELP).
