Skip to content

Commit 90dc9c3

Browse files
authored
chore(docs): info for configuring workload identity federation (#495)
1 parent 35781ed commit 90dc9c3

1 file changed

Lines changed: 12 additions & 0 deletions

File tree

README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -257,6 +257,18 @@ print_r((string) $response->getBody());
257257

258258
[iap-proxy-header]: https://cloud.google.com/iap/docs/authentication-howto#authenticating_from_proxy-authorization_header
259259

260+
#### External credentials (Workload identity federation)
261+
262+
Using workload identity federation, your application can access Google Cloud resources from Amazon Web Services (AWS),
263+
Microsoft Azure or any identity provider that supports OpenID Connect (OIDC).
264+
265+
Traditionally, applications running outside Google Cloud have used service account keys to access Google Cloud
266+
resources. Using identity federation, you can allow your workload to impersonate a service account. This lets you access
267+
Google Cloud resources directly, eliminating the maintenance and security burden associated with service account keys.
268+
269+
Follow the detailed instructions on how to
270+
[Configure Workload Identity Federation](https://cloud.google.com/iam/docs/workload-identity-federation-with-other-clouds).
271+
260272
#### Verifying JWTs
261273

262274
If you are [using Google ID tokens to authenticate users][google-id-tokens], use

0 commit comments

Comments
 (0)