From 55dd4969bac87bc5c4c37d68a7f199f085de82ed Mon Sep 17 00:00:00 2001 From: Gregory Furmanek Date: Tue, 12 Apr 2022 09:27:29 -0700 Subject: [PATCH 1/2] Update terminology from GSuite to Google Workspace Addresses: https://github.com/aip-dev/google.aip.dev/issues/818 Obsoletes: https://github.com/aip-dev/google.aip.dev/pull/858 --- aip/apps/2712.md | 2 +- aip/auth/4112.md | 6 +++--- aip/general/0002.md | 4 ++-- pages/general/faq.md | 3 ++- 4 files changed, 8 insertions(+), 7 deletions(-) diff --git a/aip/apps/2712.md b/aip/apps/2712.md index 7cf46931cf..966d58f65f 100644 --- a/aip/apps/2712.md +++ b/aip/apps/2712.md @@ -8,7 +8,7 @@ created: 2018-07-13 Our customers expect that they can be as productive in their Apps programs as they can be sitting at the UI. When they can not, this is surprising and -disappointing. Historically, G Suite has not insisted on this kind of +disappointing. Historically, Google Workspace has not insisted on this kind of completeness. However, we want to move towards that goal, hence this requirement for a plan, while we only advise completeness itself. diff --git a/aip/auth/4112.md b/aip/auth/4112.md index 7a3c992a3a..47c9838b29 100644 --- a/aip/auth/4112.md +++ b/aip/auth/4112.md @@ -10,9 +10,9 @@ created: 2020-08-13 A service account is a special kind of account used by an application or a virtual machine (VM) instance, not a person. Applications use service accounts to make authorized API calls, authorized as either the service account itself, -or as G Suite or Cloud Identity users through domain-wide delegation. Service -accounts are associated with private/public RSA key-pairs that are used for -authentication, which is the focus of this AIP. +or as Google Workspace or Cloud Identity users through domain-wide delegation. +Service accounts are associated with private/public RSA key-pairs that are used +for authentication, which is the focus of this AIP. **Note:** Because this AIP describes guidance and requirements in a language-neutral way, it uses generic terminology which may be imprecise or diff --git a/aip/general/0002.md b/aip/general/0002.md index c0e2d264a7..7f0b949f42 100644 --- a/aip/general/0002.md +++ b/aip/general/0002.md @@ -42,7 +42,7 @@ Currently recognized blocks of AIP numbers are: ### Google Product Areas -- **2700-2799:** Apps (GSuite) +- **2700-2799:** Apps (Google Workspace) - **2500-2599:** Cloud - **3000-3099:** Actions on Google - **3200-3299:** Firebase @@ -60,4 +60,4 @@ documentation germane to that specific team, reach out to api-editors@. 100-199. - **2018-10-24:** The 4600-4699 block was assigned to Google Geo. - **2018-10-02:** The 2500-2599 block was assigned to Google Cloud Platform. -- **2018-10-02:** The 2700-2799 block was assigned to Google Apps. +- **2018-10-02:** The 2700-2799 block was assigned to Google Workspace. diff --git a/pages/general/faq.md b/pages/general/faq.md index 3ee39b8825..8b722d517b 100644 --- a/pages/general/faq.md +++ b/pages/general/faq.md @@ -22,7 +22,8 @@ complete. If you see things like "Submit a CL" or "Talk to your PA lead", feel free to send pull requests to fix these oversights. (CL stands for "Change List" which is sort of like a GitHub Pull Request, and -PA stands for "Product Area" meaning things like "Google Maps" or "GSuite".) +PA stands for "Product Area" meaning things like "Google Maps" or +"Google Workspace".) ### I like most of these AIPs, but some make no sense for me. What do I do? From 9122c5b82c1b749e16cd28e1e739c1a3d3f5ff81 Mon Sep 17 00:00:00 2001 From: Gregory Furmanek Date: Fri, 15 Apr 2022 11:52:58 -0700 Subject: [PATCH 2/2] Updated tense to match the sentence. Issue: #810 --- aip/auth/4111.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aip/auth/4111.md b/aip/auth/4111.md index 2b886312b5..ee5c906434 100644 --- a/aip/auth/4111.md +++ b/aip/auth/4111.md @@ -31,7 +31,7 @@ credentials][2]. To understand the overall flow, please read [AIP-4110][2]. ### Scope vs. Audience -In the past, the self-signed JWT is only applicable with `audience`. Recently, +In the past, the self-signed JWT was only applicable with `audience`. Recently, the usage of the "scope" claim in self-signed JWTs is now allowed in the Google Cloud auth ecosystem, which makes the self-signed JWT usable with both audience and scope. However, caller **must** not specify scope and audience at the same