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.
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.
Google Cloud Platform's Tech Support directed me here.
GCP is telling me the add-on is "successfully verified and add-on is available for users." The OAuth Consent Screen confirms this.
In Developer Dashboard, the add-on is published. The "Publish in Marketplace" checkbox was checked upon submission for publication.
I've read through troves of online Google documentation, but still have not found the solution.
The docs add-on is OrangeSlice: Teacher Rubric.
ideas? Thx
It's here https://gsuite.google.com/marketplace/app/orangeslice_teacher_rubric/852746965799. You can find the link in the G Suite Marketplace SDK.
The answer is, I think, Google is very busy.
There are three advertised approval steps but it took more to get the add-on listed. It was approved first via Developer Dashboard crew. After completing the GS Marketplace Configuration and then the GS Cloud for OAuth, it was approved twice more. To the get add-on published, I needed to inform Developer Dashboard that it was approved by GS Cloud, THEN IT COULD BE RELEASED.
So if you're having issues, be persistent. The Google team answers nicely but many questions go unanswered or are ambiguous. There are many directions spread over several different pages: Marketplace, Cloud, Apps Scripts, OAuth App Verif FAQ, etc. They mostly concur but there is plenty of vagueness and inconsistency which only added to my confusion. I have 2 add-ons, one is a stripped down version of the other. The stripped down version had more hoops to jump through for approval-verification and then release than the fully loaded version. Not sure why. Again, the Google team is nice but it feels like they are swamped and/or have an intra-system communication challenges.
Here's an example.. directions within an email from the Google team:
Please follow the steps below to ensure your OAuth scope(s) request is submitted for review:
Sign-in to the Google Cloud Console
Select the project-id: api-project-#############
Go to Credentials on the OAuth Consent Screen
.....Credentials and OAuth Consent screens are two separate screens under the same heading, API Apps & Services. Neither exists within the other but next to each other.
So what to do?
When I try to publish my app on the Gsuite Marketplace via GCP, I find no way to change the setting 'Visibility'. Event if the app has never been published.
Between the two options (My Domain - Public), My domain is selected and can't be switched to Public, so nobody has access to my app.
Any help?
I've tried to contact the support and find help on forums but no answer at all.
First step, I'd recommend reviewing Choosing where to publish to ensure that you've published to the correct location. As noted under Publish your app (before you publish), your app is reviewed to determine if it meets the requirements for the relevant store. Additionally, your application may also have to undergo OAuth verification (I think this could be the problem) , and security assessment if it accesses user data, such as Gmail, Drive, Contacts, or Calendar
If your app is exempt from verification or if you've already undergone assessment and been approved, and your issue persists, I'd recommend contacting Marketplace Developer Support, via the below steps, who can assist you with your publishing issue.
Navigate to the new Developer Dashboard.
Click Contact Us.
The Developer Support contact us form is displayed.
I've tried to contact the support and find help on forums but no answer at all.
How did you contact Google Support? They have many teams and sometimes agents are not aware of the scope of support. Personally I would contact GCP Support first to verify your App in GCP, once they confirm everything is working from their end they need to route the case to GSuite with an Admin Console specialist to debug the problem
On https://glass.google.com/myglass, apps that require a login do it from the website before installing the app. How can I create an app that requires a login like this? I can't find anything in the documentation about it. Also, how can I test the app since it would not be in myglass?
Although Google has worked with some partners to get GDK-based Glassware in MyGlass that use auth, there is no public method to do so yet. This is a frequently requested feature, and you can expect that once the GDK leaves Developer Preview, it will be available.
Until then, you will need to test your app by sideloading the app onto Glass. If you're testing for yourself, you can hardcode the auth into the app, and many people have hacks that use QR codes.
Keep in mind that this only holds true for GDK Glassware. Anything built with the Mirror API has authentication as part of its web-based initialization which you can trigger without having to go through MyGlass.
Currenlty, Google Glass apps implemented with GDK do not have access to authentication support. The Google Glass team has accepted this issue to be implemented, but it is not there in XE12. Information from the Glass Team indicates that such authentication will be through the Account Manager, when it does arrive.
Only speculation and rumors about when that will be! (Though I will look at XE14 carefully when it comes out, moving Glass Android to 4.2.2 (KitKat).)
I am currently trying to make use of a FB login plugin for Wordpress.
In one of the support threads, it mentions the issue I am having is commonly fixed if you:
“Switch the “Encrypted Access Token” setting to ‘Enabled’.”
I don't have this option in the advanced app settings:
http://dl.dropbox.com/u/35816363/otto.jpg
Can someone please advise what is wrong in my app settings that this option is not available?
Thanks
Lee
Have you migrated your app to oAuth 2.0? As far as I know, that setting “Switch the “Encrypted Access Token” setting to ‘Enabled’.” will only appear when you've set your app to oAuth 2.0.
I think you could accept the migration by activating the Open Graph feature in the app settings [-> get started] (if not, I apologize in advance; I did this many moons ago ^^;) On a side note: Activating Open Graph comes with the Timeline preview in your FB profile.