Google Cloud - Project "Submit for verification" doesn't appear - google-cloud-platform

"Submit for verification" button doesn't appear after fill in information and selecting scope for my project.
We are trying to connect BigQuery to Azure Data Factory.
To be able for the 3rd party developer to work properly on collecting the data, we need to make the project "internal".
To make the project "internal", we need a Google Workspace User - except that we don't know who is the workspace user within my company.
I reached out to Google Support and they advised us to Submit the project for verification.
I followed the steps communicated by Google Support.
You can apply for verification again in the Google Cloud Console. Please note the following information:
• If scopes are selected, the scope justification fields must be filled out in order to trigger the ‘Submit for verification’ button to appear.
o Example: My app will use https://mail.google.com/ to read, compose, send, and permanently delete from Gmail. I will need read in order to____ so that my app can . I will need compose in order too, I will need send in order to____, and I will need to delete in order to____.The reason a narrower scope would not be sufficient is because ____.
After selecting a scope, I don't have a pop-up window to fill in the scope justification.
And the "Submit for verification" button doesn't appear.

Related

How to activate Groups API

This is about Control App demand,
I started my demand for
publish_to_groups,
pages_show_list,
pages_manage_posts,
pages_read_engagement
with text to describe how my software is about to use them, screen recording, test user etc. However I can't submit my demand, facebook say "You must enable Groups API".
This is where my problem is, when I try to request it, the button is disable. To make it clickable I have to make a successfull api call. How can I resolve this ?
I would like to do the same for groups_access_member_info, instagram_content_publish, instagram_basic
Thanks

Not getting the "Submit for verification" button for OAuth verification in GCP

I have created a Gmail/Calendar add-on in Google Apps Script and I want to publish it to the marketplace.
I am following the steps at https://developers.google.com/workspace/marketplace/configure-oauth-consent-screen#fill_out_the_oauth_consent_screen. I am on the "Submit for OAuth verification" step which leads to https://support.google.com/cloud/answer/9110914#submit-howto. It says:
Click the Edit App button.
Enter the information required on the configuration page, and then click Submit for verification. If the submit for verification button does not appear at the end of the configuration pages, save what you have completed and repeat steps 1-4.
I have gone through all the steps but the Submit for verification never comes up. I'm not sure what I am doing wrong?
Your first problem is that you do not have a domain name that you own/control. gmail.com and github.com are not owned by you.
Verify your site ownership
Your second problem is that you are requesting restricted scopes. Google will probably demand a security audit. Sensitive scopes can also trigger an audit.
To verify, create another client and remove the sensitive and restricted scopes and add a domain name that you own/control. To read more about the effect of scopes and possible exceptions:
Sensitive and Restricted Scopes

Google reCAPTCHA: how to generate captcha token on the server side

I've added the Google reCAPTCHA enterprise to my auth endpoints, and now I want to cover them by integration tests. To do so, I need to generate a valid token and pass it to requests. But I can't find in the docs how to do that, they only offer to create a separate reCAPTCHA key for testing environment which is not suitable for me, because I want to test production too.
I am not sure if I understood you, but I utilized test keys for testing Recaptcha using Cypress , here you can find them and more information about what you want
Copied from some source
Hello,
If you’re getting new reCaptcha keys each time you create a site then I’m afraid to say you’re doing so improperly for this scenario. Hopefully, the below instructions can help:
Log into your Google Admin Console.
Browse to the API key that you have set for your website. If you have more than 1 reCaptcha in your Admin Console you may need to click the dropdown next to the “You have ‘x’ site(s)”.
Once you’ve found your specific reCaptcha API, you’ll want to click the Settings gear icon at the top right. This will bring you to your API settings where you can grab your reCaptcha keys and add additional domains to the allow-list.
On the Settings screen you should see a list of domains in an allow-list with an input box to enter additional domains. There should be a plus sign next to this input box. Enter your domain and click the plus sign.
Finally, scroll to the bottom of the page and click the blue “Save” button. This will tell Google to apply your changes and may take up to 5 minutes to be put into place.
This will tell Google to allow the same reCaptcha keys for multiple domains specified in this allow-list on the Settings page. For further help, we’ve created an Imgur Album of a few screenshots that may help you along your way:
https://imgur.com/a/aT8J6Uu
Hopefully, with the above instructions, you’ll be able to add in your additional domains to the allow list. Should you need further assistance, we suggest reaching out to Google G Suite Admin Support.
Hope it will solve your issue
If it still didn't work in your scenario you can use the dynamic way of applying keys like saving keys into the Environment variable and based on the current environment it will be changed dynamically

AWS session timeout

Using AWS I have a lot of Chrome tabs open with multiple services. When I switch between them I am constantly getting signed out. Sometimes it's a matter of just few minutes.
AWS minimum session duration is one hour, so that's probably not the problem. How can I tackle this? Getting logged out of Lambda makes it lose all the undeployed code, this is very inconvenient.
Edit:
Answering the question in a comment: I do have multiple accounts and when I want to open a tab with a new service I just click management console (screenshot) and follow on from there. It appears to cause the actual logout.
But here's the thing - I am currently using resources only from the first account. So (since I'm within one account all the time) it shouldn't log me out right?
I see this message when I use AWS one one Account, then login to a different account in a different tab. If I return to the original tab, it recognises that I am no longer logged-into the first account and asks me to reload.
It seems that you are using SSO to login and it is generating a different set of temporary SSO credentials. Instead of using that link, select the AWS service from the search field at the top of the console, then right-click the service and "Open in New Tab". That will open the other service in a new tab, using the same login credentials.

Newly requested permissions in app settings are not reflected in the app itself

Recently i realized that i need more than basic information for my facebook application.
I need the user's birthday as well.
In my App permissions configuration i added "user_birthday" and by checking the example given by facebook the permission was added successfully.
(goes without saying that i clicked "Save changes")
when im trying to log in to my application the "user_birthday" does not appear.
(after waiting several minutes and another 24H)
any ideas what else do i need to configure in facebook?
when im trying to log in to my application the "user_birthday" does not appear.
Are you triggering the login from within your app’s code yourself?
In my App permissions configuration i added "user_birthday"
These settings are for Authenticated Referrals only. Unless your login is triggered by those, these settings will have no effect.
If you are triggering login yourself, you have to request the permission via the scope parameter.
I think what you're missing out the fact that the
permission scope
is by default not set on facebook's development plattform. It's usually done though the login link.
If you want every user to be prompted for certain permissions you need to enable "authenticated referrals" as described here.
All SDK's allow a scope parameter for the login link. You can add the scope manually to every link using a scope parameter, like so:
https://graph.facebook.com/oauth/access_token?
client_id=YOUR_APP_ID
&redirect_uri=YOUR_REDIRECT_URI
&client_secret=YOUR_APP_SECRET
&code=CODE_GENERATED_BY_FACEBOOK
&scope=user_about_me,user_birthday