As a developer using Google API, I received the email "Migrate to the new Google Identity Services library". Our application has both Web-based and client solutions. We use Google Sign-In JavaScript library in the Web-based solution, which needs to be migrated. Our client solution calls the GetAuthorizationUrl() method of OAuth2ProviderForApplications in Google API .NET library to get the authorization URL and launch a browser window with the URL.
Is the URL from the .NET library affected by this migration?
I compared the URLs in the windows launched by both Google Sign-In and GIS and those from the .NET library. There seemed to be some difference:
GIS:
https://accounts.google.com/o/oauth2/v2/auth/oauthchooseaccount?...
Google Sign-in Javascript:
https://accounts.google.com/o/oauth2/auth/oauthchooseaccount?...
Google API .NET library:
https://accounts.google.com/o/oauth2/auth?...
#2 and #3 are currently used in our system. When upgraded from Google Sign-in (#2) to GIS (#1), the authorization URL has "v2".
Is the "non v2" version of the authorization URL endpoint (#3) still valid after migration? As we will keep getting this non-v2 URL from the .NET library, it is important to make sure it is still working to avoid our service interruption.
Related
I am currently implementing Google authentication on my client's website (back in Symfony), and would like to install the Google SDK on its API (https://developers.google.com/identity/sign-in/web/backend-auth). The situation is such that we can't install this SDK for the moment (deep dependency conflict).
Could we use (temporarily) tokeninfo api endpoint instead of the Google PHP SDK recommended by Google for production ?
according to google:
The older Google Sign-In platform library:
apis.google.com/js/platform.js, and Google APIs client library for
JavaScript: gapi.client, are no longer required for user
authentication and authorization. They have been replaced by a single
new Google Identity Services JavaScript library:
accounts.google.com/gsi/client.
with the older library you could both authenticate users to your site and you could make authorized requests to google api such as calendar.
there is no information in the docs, as far as i can see, reagrding how to make authenticated requests to google api's such as calendar.
is the new api only replacing the old for apps that only do sign in.
am i missing a way of using the new api to make authenicated requests.
FYI:
On Feb/15/2022, Google announced the availability of Authorization in Google Identify Service SDK:
https://developers.googleblog.com/2022/02/announcing-authorization-support-for.html
here is the docs:
https://developers.google.com/identity/oauth2/web/guides/overview
i installed alfresco community edition on GCP virtual machine in linux process is done alfresco is up but I cannot connect my Alfresco community edition to google drive. how to connect alfresco with google drive?
Every request your application sends to the Drive API must include an authorization token. The token also identifies your application to Google. Your application must use OAuth 2.0 to authorize requests. No other authorization protocols are supported. If your application uses Google Sign-In, some aspects of authorization are handled for you.
Please follow the link to know better about the google drive integration.
I am implementing Cloud Endpoints with a Python app, I need to expose the restAPI in a secure way https (this is authomatic), The consumer of this Endpoint will be a java Application (not a web browser or app android or ios), and my questions is if there are any way to limit the consume od this Services only for that application.
I've seen "Service Account" oauth but i don't know if i can use it for this problem and if is possible i don't know how to configure it.
Thanks a lot.
Does anyone know if there are any CalDav web clients or even any client libraries that will connect to the Google Calendar CALDAV API/server (we the recent oAuth2 additions)? We want to do this so that Google calendars can be managed in a standard way, and embedded in our own application.
One possible library is gaye/dav on github. It was initially written for Firefox OS and provides support for an OAuth2 transport.
That aside, adding OAuth2 support to any other existing library is probably not that hard. When you know it is a Google CalDAV server, do the OAuth exchange to get the access token. Then, if the library has a hook (or a function that can be monkeypatched) that runs just before a request is sent, set the request header Authorization: Bearer <oauth access token> with each request.