googleapis/google/iam
2019-12-04 11:49:37 -08:00
..
admin/v1 chore: publish retry configs for iam admin, cloud asset, and remoteworkers 2019-12-04 11:49:37 -08:00
credentials feat: publish several retry config files for client generation 2019-12-03 13:50:12 -08:00
v1 Populate BAZEL.build files for around 100 APIs (all APIs we publish) in all 7 langauges. 2019-11-25 15:50:18 -08:00
artman_iam.yaml Synchronize new proto/yaml changes. 2018-07-25 14:29:39 -07:00
artman_iam_admin.yaml Synchronize new proto/yaml changes. 2018-07-25 14:29:39 -07:00
artman_iam_meta_api.yaml Synchronize new proto/yaml changes. 2019-05-06 14:24:09 -07:00
BUILD.bazel Use rules_proto bzl files to load proto_library 2019-11-13 22:28:15 -08:00
iam.yaml Add LRO service config. Update Pub/Sub. Remove unneeded context. (#155) 2016-09-27 09:15:54 -07:00
iam_meta_api.yaml Synchronize new proto/yaml changes. 2019-05-06 14:24:09 -07:00
README.md Revert "Synchronize new proto/yaml changes." (#554) 2019-05-29 14:23:10 -07:00

Introduction

Key Concepts

Service Account

A Service Account is an account used to identify services (non-humans) to Google. A Service Account has a list of Service Account Keys, which can be used to authenticate to Google.

Service Account Keys

A Service Account Key is a public/private keypair generated by Google. Google retains the public key, while the customer is given the private key. The private key can be used to sign JWTs and authenticate Service Accounts to Google.