


How do I authenticate to GCP using an uploaded (not generated) service account key?
php editor Strawberry will introduce you in detail how to use the uploaded service account key to authenticate Google Cloud Platform (GCP). Authentication is a very important step in the process of using GCP, and the service account key is the key to authentication. This article will explain to you how to upload the service account key and authenticate it correctly so that you can smoothly use various functions and services of GCP. Whether you are new to GCP or have some experience, this article will provide you with useful guidance and tips to ensure that you can complete the authentication process with ease. By reading this article, you will learn the steps and considerations for uploading service account keys, and how to correctly use these keys for authentication in GCP.
Question content
I am writing a service that requires different tenants to access GCP services. My microservices will be running on different hosts (no GCP). One of the limitations I'm facing is using a service account key to authorize api calls. The second constraint is that my microservice is responsible for generating the key pair for the service account and sharing the public key with the tenants so that they can upload it to their service account.
My current problem is that I can't find any documentation that explains how to authenticate to the GCP golang library using the key pair I have. All the documentation I've read always addresses service account key authentication, assuming that you will let GCP generate the key pair for you, and that you already have a json file with all the details you need.
Documents I have reviewed:
- https://cloud.google.com/docs/authentication/client-libraries#adc - https://cloud.google.com/docs/authentication#service-accounts - https://cloud.google.com/docs/authentication/provide-credentials-adc#local-key - https://github.com/GoogleCloudPlatform/golang-samples/blob/main/auth/id_token_from_service_account.go
Google Libraries uses a mechanism called "Application Default Credentials" that allows all of its libraries to find credentials for authentication. Specifically, in this case, the ADC always requires the json file to get the details of the credentials.
The json file looks like this:
<code>{ "type": "service_account", "project_id": "my-project", "private_key_id": "1ed3aae07f98f3e6da78ad308b41232133d006cf", "private_key": "-----BEGIN PRIVATE KEY-----\n...==\n-----END PRIVATE KEY-----\n", "client_email": "<EMAIL HERE>", "client_id": "1234567890102", "auth_uri": "<GOOGLE AUTH URI HERE>", "token_uri": "<GOOGLE TOKEN URI HERE>", "auth_provider_x509_cert_url": "<SOME GOOGLE URL HERE>", "client_x509_cert_url": "<MORE GOOGLE URL HERE>", "universe_domain": "googleapis.com" } </code>
So my question is, how do I build this json file from the generated key pair? If this is not possible (GCP limitation), then why am I able to upload the key pair? Can anyone point me to an example to help me resolve this situation?
Any help is greatly appreciated
I've reviewed all GCP official documentation, API reference, and Github script examples. None of them referenced the uploaded service account key
Workaround
It took me a while to get back to this issue. Thanks to @guillaume-blaquiere's answer, I started testing with the minimal required files.
Finally came up with this:
{ "type": "service_account", "private_key": "<Your generated private_key.pem>", "client_email": "<service account email>", }
These are the minimum properties required by the Google SDK to successfully authenticate to GCP
The private key must be the same one used to generate the public key uploaded to the GCP service account.
As far as golang code is concerned, you can put this information into a structure and then parse the structure into json:
type JSONFile struct { Type string `json:"type"` PrivKey []byte `json:"private_key"` Email string `json:"client_email"` }
Then:
file := JSONFile{ Type: "service_account", PrivKey: "<PK bytes here>", Email: "<a href="https://www.php.cn/link/89fee0513b6668e555959f5dc23238e9" class="__cf_email__" data-cfemail="7d0e180f0b141e18501c1e1e120813095018101c14113d1a1e0d531e1210">[email protected]</a>", } result, err := json.Marshal(file) if err != nil { panic(1) } credentials, err := google.CredentialsFromJSON(context.Background(), result, secretmanager.DefaultAuthScopes()...) if err != nil { panic(1) } projectsClient, err := resourcemanager.NewProjectsClient(context.Background(), option.WithCredentials(credentials))
The above is the detailed content of How do I authenticate to GCP using an uploaded (not generated) service account key?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...

What should I do if the custom structure labels in GoLand are not displayed? When using GoLand for Go language development, many developers will encounter custom structure tags...

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

This article introduces how to configure MongoDB on Debian system to achieve automatic expansion. The main steps include setting up the MongoDB replica set and disk space monitoring. 1. MongoDB installation First, make sure that MongoDB is installed on the Debian system. Install using the following command: sudoaptupdatesudoaptinstall-ymongodb-org 2. Configuring MongoDB replica set MongoDB replica set ensures high availability and data redundancy, which is the basis for achieving automatic capacity expansion. Start MongoDB service: sudosystemctlstartmongodsudosys
