Is there New API replacing the current API:
https://developers.google.com/admin-sdk/admin-settings/
If not, why are they removing such a feature?
Warning: The Admin Settings API is deprecated and is scheduled to be sunset on October 30, 2017.
In addition, the current API does not support the full functions of the G Suite Admin console. For example, there is nothing on Inbound Mail Gateway and nothing on Managing API Access in the Security Settings
Thank you very much!
Since it is schedule to be sunset on October 30, 2017, the Google still has 7 months to annonce if they will replace it with another API or they will totally shut down this API. I suggest you to always check the Google Developers Blog about the announcement for their API release and updates.
For more information, check these blogs:
Saying Goodbye to the GData Admin Settings API
Google to Sunset GData Admin Settings API
Related
I got a warning from google stating "your client ID(s) use the legacy Google Sign-In web solution".
And we are asked to migrate to the new Google Identity Services.
We do not use any JS library to sign-in. We have a Google PHP Client library for authentication and authorization.
Google still flagged our client Id and advised to migrate before March 31 2023.
Will this depreciation really affect us?
Can someone help me with the exact changes to be done on our end?
The team has a system that can detect which projects are calling the endpoint used by the deprecated JavaScript sign-in library. They send out emails to the owners of that project. From what I understand from the team they don't know for a fact that you are using it they can just see that your project id is hitting it.
The Google APIs PHP client library does not hit this end point so that part of your code is not the source.
I would just double check around your team and make sure nothing else may be using the old JavaScript library. If you cant find anything then the easiest solution is to just wait once google starts rolling out the deprecation at the end of March someone will come find you if something breaks.
We are trying to integrate Facebook analytics into our apps and we notice that user properties has been deprecated on 22 Jun 2020. But doc doesn't not say anything about the alternative way. Is there any means to add new user properties like this in Firebase analytics?
We are using GitKit API in production projects - and there is an urgent need to change the domain of one of our existing projects.
This is normally done under Google Cloud Console - in API Manager under "Identity Toolkit API" -> "Edit" link. Unfortunately, this link is gone - it was probably removed this week?!
We know the new projects should use Firebase Authentication (as announced on Google I/O this year) and we have started to work on upgrading our auth code and we are keen on using it in new projects.
But our existing production projects cannot be migrated easily!
We have not been alerted anyhow in advance, that "Edit" on existing projects will be disabled - and there is no deprecation date specified at https://developers.google.com/identity/toolkit/migrate-firebase or in the alert messages. As paying Google Apps customers we rely on many Google products. This is a very unpleasant surprise.
Is there any way how to restore the "Edit" for "Identity Toolkit API" for existing projects? As I said, we urgently need to adjust a domain of an existing production project. Any help from the Google engineers would be greatly appreciated.
Sorry for the inconvenience. We have rolled out the fix, and the Identity Toolkit API setting page should work now.
Recently, AuthSub died...?
Is it possible to migration from session_token of Authsub to refresh_token of OAuth2 ?
Please tell me how to do it if possible.
Its still supported, but is failing for us as well (and others if search twitter for it). I'm wondering if Google is experience a technical issue with AuthSub or if they made a change (e.g. patch/release) earlier this week that is causing the issues?
We see it working for some Google accounts and fail for others - starting on Dec 10/11. So, its not impacting every Google account.
We are currently not capturing the outgoing requests to google. We are using the library gdata-calendar-1.0.jar to make google calendar api calls using AuthSub and the library is throwing an exception with the exception message "Unknown authorization header". This worked perfectly up until Dec 10/11th or so for all of our users.
What is strange is now the same calls do work for certain gmail accounts but not for others.
In our testing we are seeing that turning off the enhanced security in our web application results in the warning displayed to the user on the Google Authorization page but makes the connection work for the accounts that are failing.
Here are the api calls we are making:
AuthSubUtil.exchangeForSessionToken to connect to the google account
CalendarService.query to get events
CalendarService.insert to insert events in calendar
CalendarService.getFeed to get the calendars
AuthSub is still supported by Google as per Google's deprecation policy.
As for a migration path to OAuth2, currently there is none.
Facebook provides developers with a test account for testing purpose, does Instagram provide any test account similar to what Facebook provides?
Instagram does not provide test accounts in the same sense Facebook does.
Instagram provides an API Console (powered by Apigee) to test your API calls. For calls requiring an authenticated user you would need to use an existing Instagram account.
UPDATE
Instagram now provides a Sandbox mode for all new applications.
From Instagram
Apps created on or after Nov 17, 2015 can take advantage of Sandbox mode right away. Apps created before this date will only be able to use Sandbox mode after June 1, 2016, but can still start submitting for review. On June 1, 2016 any app that has not been reviewed and approved will be set to sandbox mode.
More info in the Instagram docs.
You can create a Facebook test user, Login on Facebook and then sign up with Facebook test user on Instagram.com
This works for me!