addressing review

This commit is contained in:
aeitzman 2023-03-22 11:42:52 -07:00
parent 0560e509a2
commit af288081ce
1 changed files with 5 additions and 5 deletions

View File

@ -26,7 +26,7 @@
// //
// Using workload identity federation, your application can access Google Cloud // Using workload identity federation, your application can access Google Cloud
// resources from Amazon Web Services (AWS), Microsoft Azure or any identity // resources from Amazon Web Services (AWS), Microsoft Azure or any identity
// provider that supports OpenID Connect (OIDC). // provider that supports OpenID Connect (OIDC) or SAML 2.0.
// Traditionally, applications running outside Google Cloud have used service // Traditionally, applications running outside Google Cloud have used service
// account keys to access Google Cloud resources. Using identity federation, // account keys to access Google Cloud resources. Using identity federation,
// you can allow your workload to impersonate a service account. // you can allow your workload to impersonate a service account.
@ -39,7 +39,7 @@
// Amazon Web Services (AWS): https://cloud.google.com/iam/docs/workload-identity-federation-with-other-clouds#aws // Amazon Web Services (AWS): https://cloud.google.com/iam/docs/workload-identity-federation-with-other-clouds#aws
// Microsoft Azure: https://cloud.google.com/iam/docs/workload-identity-federation-with-other-clouds#azure // Microsoft Azure: https://cloud.google.com/iam/docs/workload-identity-federation-with-other-clouds#azure
// OIDC identity provider: https://cloud.google.com/iam/docs/workload-identity-federation-with-other-providers#oidc // OIDC identity provider: https://cloud.google.com/iam/docs/workload-identity-federation-with-other-providers#oidc
// SAML identity provider: https://cloud.google.com/iam/docs/workload-identity-federation-with-other-providers#saml // SAML 2.0 identity provider: https://cloud.google.com/iam/docs/workload-identity-federation-with-other-providers#saml
// //
// For OIDC and SAML providers, the library can retrieve tokens in three ways: // For OIDC and SAML providers, the library can retrieve tokens in three ways:
// from a local file location (file-sourced credentials), from a server // from a local file location (file-sourced credentials), from a server