We need to upgrade google sign-in (I believe it is used in both react and angular part)
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.
Hello Google Developer,
You are receiving this message as a reminder that one or more of your web applications uses thelegacy Google Sign-In web solution. Ourannounced planstated that support for theGoogle Sign-In JavaScriptplatform library will be deprecated afterMarch 31, 2023.
After March 31, 2023, migration to the newGoogle Identity Servicesis recommended to sign in customers using their Google Account to your platform. The SDK will use the new Sign in with Google client library.
What do I need to know?
To help you find out which of your web apps or environments are affected, we’re sharing a list of your client ID(s) that use the legacy Google Sign-In web solution. This list should help you evaluate user impact and prioritize the migration work more efficiently:
App Name | Client ID
-- | --
Instea SSO | 914978031481-bk8e8bj1ur0vhq4qlh7n7875drin9r0e.apps.googleusercontent.com
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.
Hello Google Developer,
You are receiving this message as a reminder that one or more of your web applications uses the [legacy Google Sign-In web solution](https://notifications.google.com/g/p/AM0Oveqx_JGPDe5OmaA46i-zw0g_bE9xw006poVdwAHiT3cEG4dmEMDT5AlzU6oquvNvQbO0TcSAAwcEYphOAaDwR_vCS80p2Az8SbZ30V0AJUfGjLF_4mU4pI7VzCi9Mr1G1p-LWcHCkq4Yd2KFKt3dW9behOG4n3kX2NUXFzf-wZLieh-KYz8Eym0VB525YJQNmR6-KN0ghVjF7HevxGfV3AwsRTacybd3). Our [announced plan](https://notifications.google.com/g/p/AM0OveqUDzU925lkayavF0oDgxQRKizhF3qjduAbD3qBAoxsaRRRuR7i_XdIaurxtFkl3uUEpVKzAu2Jr4bgZA3TfqD5_JgB8fhc5Q5QV1ZxhA0Rs2roxzXX0OlQO3urNDzIJSAi7ga41Y-dvmqv7-CTFDut-tiluayrjDcIoVg3VarDY-XuMKkTaBPVkmFltTykuEw6l33cWExHePPy-A9Z4eFkg4togystzu7NfyyrEdQUrqCHwVM) stated that support for the Google Sign-In JavaScript platform library will be deprecated after March 31, 2023.
After March 31, 2023, migration to the new [Google Identity Services](https://notifications.google.com/g/p/AM0OverpV3X3A7yg5XKDq6b-GglPrdVV0N7S9es3udhzSAuG5NPyb1Q7E9_R5Rqd5Az1BhSTtUYQqFNTKAsZ49BB1v9PzxhIaNsT0xe84xJFH95LoE-oKeWIB3WkV0uuJg0SqpXBdN-VpBbaexP_Wf_8uu7eYVpAtu0saKhhShpb0Z2I7iXS9dODeNWkirRyJLCVbf0m7U3hMp9ZG9Jfo81OEZXv9rD0jRlgb4qW80cpXHq5YPBgvcfciYPvivGc8C7PT6lrCpprJkMfWUPm) is recommended to sign in customers using their Google Account to your platform. The SDK will use the new Sign in with Google client library.
What do I need to know?
To help you find out which of your web apps or environments are affected, we’re sharing a list of your client ID(s) that use the legacy Google Sign-In web solution. This list should help you evaluate user impact and prioritize the migration work more efficiently:
App Name Client ID
Instea SSO 914978031481-bk8e8bj1ur0vhq4qlh7n7875drin9r0e.apps.googleusercontent.com
What do I need to do?
Please migrate to the new Google Identity Services by following guides for [authorization](https://notifications.google.com/g/p/AM0Oveqey8dP7recPxZ5QYSHI3F8RW7CRk1tLju8N3nrjo6Vr_uT9EZzKMZ2DFFHMM_L42_ZrSRJHMtZV-WWDOzdTJ_6IyOmzFtTB65gYOAHMnDPI1u_toWRn38JZfdspbt-rFtRWGwe98m4Vh0ORTilferfasBlglkNFt_Yvuq1XZvEAh7oZY7evIwg2Oynjj2WuwGMl7OZCBfb-llcXBZ8WCfHO9sW9WP1Ff5mn7sM1Q) and [authentication](https://notifications.google.com/g/p/AM0OveoVJjTNEBSAdok-pL-vlzfUs2jLtBKd_N-2U6QRHIKiKh1R25DdEoWdXdSkE1fTRAM54kNJ8v6zOvaBAWlcC6zG-Dh_1ehEM5qg0SCDlIODcZtEQBL1V8FrwoilTe248BwIbiaOm8RixNCyva77uT8DtJr8u06vC2goqYXQNYqPxY6J5p_tvDwbW36iovOX6n2N9j3InUuad_Cq5DwSeb-n5DtYNVJ1DYvUEw).
Be sure to read through the [Sign in with Google resources](https://notifications.google.com/g/p/AM0Oveqey8dP7recPxZ5QYSHI3F8RW7CRk1tLju8N3nrjo6Vr_uT9EZzKMZ2DFFHMM_L42_ZrSRJHMtZV-WWDOzdTJ_6IyOmzFtTB65gYOAHMnDPI1u_toWRn38JZfdspbt-rFtRWGwe98m4Vh0ORTilferfasBlglkNFt_Yvuq1XZvEAh7oZY7evIwg2Oynjj2WuwGMl7OZCBfb-llcXBZ8WCfHO9sW9WP1Ff5mn7sM1Q) guide. If you have migration specific feedback to share, send an email to [gis-migration-feedback@google.com](mailto:gis-migration-feedback@google.com).
misosviso
commented
1 year ago
We need to upgrade google sign-in (I believe it is used in both react and angular part)
Hello Google Developer,
You are receiving this message as a reminder that one or more of your web applications uses the legacy Google Sign-In web solution. Our announced plan stated that support for the Google Sign-In JavaScript platform library will be deprecated after March 31, 2023.
After March 31, 2023, migration to the new Google Identity Services is recommended to sign in customers using their Google Account to your platform. The SDK will use the new Sign in with Google client library.
What do I need to know?
To help you find out which of your web apps or environments are affected, we’re sharing a list of your client ID(s) that use the legacy Google Sign-In web solution. This list should help you evaluate user impact and prioritize the migration work more efficiently:
App Name | Client ID -- | -- Instea SSO | 914978031481-bk8e8bj1ur0vhq4qlh7n7875drin9r0e.apps.googleusercontent.comWhat do I need to do?
Please migrate to the new Google Identity Services by following guides for authorization and authentication.
Be sure to read through the Sign in with Google resources guide. If you have migration specific feedback to share, send an email to gis-migration-feedback@google.com .
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. Hello Google Developer, You are receiving this message as a reminder that one or more of your web applications uses the [legacy Google Sign-In web solution](https://notifications.google.com/g/p/AM0Oveqx_JGPDe5OmaA46i-zw0g_bE9xw006poVdwAHiT3cEG4dmEMDT5AlzU6oquvNvQbO0TcSAAwcEYphOAaDwR_vCS80p2Az8SbZ30V0AJUfGjLF_4mU4pI7VzCi9Mr1G1p-LWcHCkq4Yd2KFKt3dW9behOG4n3kX2NUXFzf-wZLieh-KYz8Eym0VB525YJQNmR6-KN0ghVjF7HevxGfV3AwsRTacybd3). Our [announced plan](https://notifications.google.com/g/p/AM0OveqUDzU925lkayavF0oDgxQRKizhF3qjduAbD3qBAoxsaRRRuR7i_XdIaurxtFkl3uUEpVKzAu2Jr4bgZA3TfqD5_JgB8fhc5Q5QV1ZxhA0Rs2roxzXX0OlQO3urNDzIJSAi7ga41Y-dvmqv7-CTFDut-tiluayrjDcIoVg3VarDY-XuMKkTaBPVkmFltTykuEw6l33cWExHePPy-A9Z4eFkg4togystzu7NfyyrEdQUrqCHwVM) stated that support for the Google Sign-In JavaScript platform library will be deprecated after March 31, 2023. After March 31, 2023, migration to the new [Google Identity Services](https://notifications.google.com/g/p/AM0OverpV3X3A7yg5XKDq6b-GglPrdVV0N7S9es3udhzSAuG5NPyb1Q7E9_R5Rqd5Az1BhSTtUYQqFNTKAsZ49BB1v9PzxhIaNsT0xe84xJFH95LoE-oKeWIB3WkV0uuJg0SqpXBdN-VpBbaexP_Wf_8uu7eYVpAtu0saKhhShpb0Z2I7iXS9dODeNWkirRyJLCVbf0m7U3hMp9ZG9Jfo81OEZXv9rD0jRlgb4qW80cpXHq5YPBgvcfciYPvivGc8C7PT6lrCpprJkMfWUPm) is recommended to sign in customers using their Google Account to your platform. The SDK will use the new Sign in with Google client library. What do I need to know? To help you find out which of your web apps or environments are affected, we’re sharing a list of your client ID(s) that use the legacy Google Sign-In web solution. This list should help you evaluate user impact and prioritize the migration work more efficiently: App Name Client ID Instea SSO 914978031481-bk8e8bj1ur0vhq4qlh7n7875drin9r0e.apps.googleusercontent.com What do I need to do? Please migrate to the new Google Identity Services by following guides for [authorization](https://notifications.google.com/g/p/AM0Oveqey8dP7recPxZ5QYSHI3F8RW7CRk1tLju8N3nrjo6Vr_uT9EZzKMZ2DFFHMM_L42_ZrSRJHMtZV-WWDOzdTJ_6IyOmzFtTB65gYOAHMnDPI1u_toWRn38JZfdspbt-rFtRWGwe98m4Vh0ORTilferfasBlglkNFt_Yvuq1XZvEAh7oZY7evIwg2Oynjj2WuwGMl7OZCBfb-llcXBZ8WCfHO9sW9WP1Ff5mn7sM1Q) and [authentication](https://notifications.google.com/g/p/AM0OveoVJjTNEBSAdok-pL-vlzfUs2jLtBKd_N-2U6QRHIKiKh1R25DdEoWdXdSkE1fTRAM54kNJ8v6zOvaBAWlcC6zG-Dh_1ehEM5qg0SCDlIODcZtEQBL1V8FrwoilTe248BwIbiaOm8RixNCyva77uT8DtJr8u06vC2goqYXQNYqPxY6J5p_tvDwbW36iovOX6n2N9j3InUuad_Cq5DwSeb-n5DtYNVJ1DYvUEw). Be sure to read through the [Sign in with Google resources](https://notifications.google.com/g/p/AM0Oveqey8dP7recPxZ5QYSHI3F8RW7CRk1tLju8N3nrjo6Vr_uT9EZzKMZ2DFFHMM_L42_ZrSRJHMtZV-WWDOzdTJ_6IyOmzFtTB65gYOAHMnDPI1u_toWRn38JZfdspbt-rFtRWGwe98m4Vh0ORTilferfasBlglkNFt_Yvuq1XZvEAh7oZY7evIwg2Oynjj2WuwGMl7OZCBfb-llcXBZ8WCfHO9sW9WP1Ff5mn7sM1Q) guide. If you have migration specific feedback to share, send an email to [gis-migration-feedback@google.com](mailto:gis-migration-feedback@google.com).