You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use Google authentication in our carta-controller deployment at ASIAA.
I have received an email from Google stating: [Action Required] Migrate to the new Google Identity Services library as soon as possible
One or more of your web applications uses the legacy Google Sign-In JavaScript library. Please migrate your project(s) to the new Google Identity Services SDK before March 31, 2023.
I think that once the OIDC stuff is merged in it should no longer to be necessary to have that separate Google auth process working. I tested using Google as IDP during the dev of that OIDC auth configuration to verify that it'd work and also had some students report success using it here as well.
We use Google authentication in our carta-controller deployment at ASIAA.
I have received an email from Google stating:
[Action Required] Migrate to the new Google Identity Services library as soon as possible
One or more of your web applications uses the legacy Google Sign-In JavaScript library. Please migrate your project(s) to the new Google Identity Services SDK before March 31, 2023.
They provide a link to Instructions on how to do so: https://developers.google.com/identity/gsi/web/guides/migration
It looks like it will be easy to do, only requiring changes to a few lines.
The text was updated successfully, but these errors were encountered: