IssueTracker

+1 here too. But the problem is also with disks. We currently use part of hostname in the name. Sometimes a machine has to be renamed and it's not possible.

+1

Hello,

Thanks for reaching out to us!

The Feature Request has been created and the Product Engineering Team is working on this request. At this moment, there is no ETA to this request. Thank you for your trust and continued support to improve Google Cloud Platform products.

In case you want to report a new issue, please do not hesitate to create a new Issue Tracker thread describing your issue.

+1 Any updates on this?

Please refrain from submitting "+1" comments that spam everyone subscribed to issues here on Google (or for that matter in almost all modern issue trackers). It isn't the Apache board in 1998. Vote and subscribe to issues. Or at least add some meaningful information to your comments. Thank you for your understanding.

My assigned has same trouble and they would like to solve this issue,

They have created a mechanism to automatically build multiple development environments. Although the creation of other services can be automated, only the OAuth2.0 client settings have to be handled manually. Please be able to do the following to improve the development cycle:

• Capability to add, remove, and edit oAuth approved redirect URIs from the command line
• Partial wildcard support for oAuth approved redirect URIs.

So tiered of all the limitations GCP have when it comes to oauth. Just like most people here, I need to be able to define Redirect URIs.

I really don't want to host my own oauth solution, but with all the limitations that GCP has around it, I'm starting to lean towards hosting our own keycloak or similar tool is the only long term solution. How are we supposed to scale with these kinds of limitations?

I'm not from the Terraform or OAuth Teams, But I just tried this and it is working for me:

https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/identity_platform_config

This is Ideal if you have not already enabled Identity Platform on your Google Cloud Project as it will enable it for you as if you pressed the big blue "Enable Identity Platform" button on the GCP console for a new project.

If you already have an Identity Platform enabled on your GCP Project, then you can try and import with terraform import google_identity_platform_config.default "my-gcp-project" once you have added the below to your terraform config:

resource "google_identity_platform_config" "default" {
  project                    = var.project_id
  autodelete_anonymous_users = true

  authorized_domains = [
    "localhost",
    "my-gcp-project.firebaseapp.com",
    "my-gcp-project.web.app",
    "${var.dns_domain}",
    "api.${var.dns_domain}",
  ]
}

Heck, I'd be ecstatic to just get an API to map from the human readable name to the set of strings needed to run an OIDC authentication:

• client_id
• client_secret
• a few global (presumably, at least when limited to google) URLs

That would be enough that I could at least use a Terraform data resource to fill in blanks on other resources.

We need this as well.

What do you think about the idea of ​​implementing changing Authorized JavaScript Origins and Authorized Redirect URIs programmatically instead of manually in the GCP console?

Identity Platfrom includes a lot of functionality and requires support for it on clients. I would like to stay on simple and convenient OAuth clients that can be fully managed via API.