IssueTracker

Can you elaborate on the end goal/use-case? We have service accounts that are designed for non-interactive authentication: https://cloud.google.com/docs/authentication

We both use Service accounts, API keys and OAuth client credentials in our projects. The first two types can be created using the gcloud command, such as 'gcloud beta iam service-accounts create some-account --display-name "My Service Account"' for a Service Account.

OAuth client credentials don't seem to be able to be created using the gcloud command as far as we know and need to be created through the developer console. Since we create new projects from time to time and setup our environments in those projects in an almost automated way, this step means we have to manually create the OAuth client credentials ergo blocking our automation.

Being able to automate changes to the consent screen with gcloud CLI would be very useful. Updating configuration for: Email address, Product name, Homepage URL, Product logo URL, Privacy policy URL, Terms of service URL.

Same thing here but directly from an API.

There's https://cloud.google.com/resource-manager/docs/ to create a project,

but can't find any API to configure the Concent Oauth Screen and create new OAuth / API Keys.

Would be great to avoid unpleasing manual configuration for a lot a projects

thanks

We need this as well to be able to fully automate our projects. Our use case is using Cloud Identity-Aware Proxy which requires setting up the OAuth consent screen.

We enable IAP programmatically for a large volume of backend services which are deployed by our development team for testing and review. Currently we have to use a horrible cludge and scrape the curl command out of the GUI. Why isn't this entity available via the API?

The ability to add redirect URLs for existing ClientIDs would also be great

https://cloud.google.com/iap/docs/reference/app-engine-apis - this documentation describes how to enable the IAP via gcloud and the API. The ClientID is required . Seems quite strange that you would need to manipulate something in the GUI before being able to call this endpoint....

+1

Great!! Thanks.

Hi, I made a feature request for the ability to set a project's authorized domains, developer contact information, and scopes on the OAuth consent screen via an API.
https://issuetracker.google.com/issues/186147991

Got told to ask about it on here, is it already being worked on?

I'm waiting too.

I need this also, please.

+1

My first task on gcloud - create consent screens and oauth clients for multiple projects.
Can't be automated.
First impressions.

+1

+1

+1

Our use case is creating production like GCP developer environments per pull request/on demand for our engineers. This is the only part that can't be automated :(

Same here - automation for setting up different client IDs for different branch-specific development environments; this is needed because each branch development environment has its own dynamic URL, hence different client ID is needed, or an API to update the allowed redirect URIs.

+1

+1

+1

+1

+1

+1
I need to automation entire process of setting up and tearing down applications, and not having this is a roadblock.

+1
Have a customer(Accenture) that needs this as well.

+1