I am using Google Apps for my domain jkltech.in, I wanted to sign my e-mails with DKIM Keys as I am using Google App Engine for my website.
I have registered my TXT Record with my DNS provider, but I am unable to start authentication in my Google Apps Account. I am using Google Apps for Free. I have verfied my DNS entry using various tools such as dig and other online tools, http://www.protodave.com/security/checking-your-dkim-dns-record/
Do let me know what I am missing, is my TXT record wrong or is there some other issue with my configuration,
Regards,
Jay
this is apparently a known issue and they're still working on a fix. See the Google Product Forum thread at https://productforums.google.com/d/topic/apps/FOsrXULt66Y/discussion. Cheers.
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?
my dev and I would like to implement the google picker on our website. It will allow the web-visitor to upload their files from their Google drive to our website.
My dev is now trying to get the API for the google picker however they are asking for a "demo video that showcases the process to request an OAuth token" and we were wondering how we should do it when we don't have the API from google.
We are doing all of this on the staging site and we were wondering how are we suppose to do this demo video when the API is not provided and not installed.
please enlighten us, thank you!
See the question How can I make sure the verification process is as streamlined as possible? in the FAQ. It explains what the verification team is looking for with the video. Mostly it's just about showing how your product uses OAuth and the various APIs -- in your case how it asks for access to Drive, how the picker is used, etc. You're showing the integration from the user perspective.
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
I privately host a site for my family that uses the Google Spreadsheets API (readonly). I received an email from google looking to "Remove risky access to your data". My site is listed with a warning:
I've gone through the verification process (filling out this form: https://support.google.com/code/contact/oauth_app_verification) but got the response that if the site is used privately "you don't need to go through the verification process". They state this in their FAQ also: OAuth Developer Verification Form FAQ.
However, the site still shows a warning in Google's security check-up. I can ignore this but I think other family members will be worried unnecessarily OR ignore future warnings about other apps assuming it's the family one they normally ignore.
Is there a way to verify myself as a developer of a private site or mark the access as trusted so the warning doesn't recur?
I ended up making my site public and going through the usual verification process.
Not really an answer, but rather to flag that this is an issue my dilemma as well. Although I run time-based Google Script within an organization. I've contacted folks at the Google Cloud Platform and they have opened a case. However, here is something interesting I've stumbled across just now. Go to your Google account and do Security Checkup
After the checkup your screen might be showing something like this
Try clicking "Dismiss" to prevent Google from removing your app.
I'm just testing it myself and if in an hour (that's how long it usually takes Google to remove your own script from the list of self-authorized apps with access to account info) Google won't remove it, I guess it would work for me!