Skip to content

Commit c215703

Browse files
authored
Update consumer_journey.md (#877)
OAuth updates - expanding the "Request credential" section to mention credential reuse
1 parent 7b94ba3 commit c215703

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

content/en/docs/Overview/consumer_journey.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,12 @@ This step ensures that usage is governed by provider-defined policies and access
3030

3131
## Request credentials
3232

33-
To authenticate and consume the product resources, consumers can generate or request **credentials** (such as API keys or OAuth tokens).
33+
To authenticate and consume the product resources, consumers can generate or request **credentials** (such as API keys, OAuth tokens, or certificates).
34+
3435
Amplify Engage automates credential issuance and ties them to the consumer’s subscription.
3536

37+
When requesting access to an API service that shares an Identity Provider with another API service you already have a credential for, Engage notifies you that the existing credential can be reused — no new secrets are generated. The result is a single credential that works across all API services sharing the same OAuth server.
38+
3639
## Gain insights into consumption
3740

3841
Consumers can view **insights** into their API consumption, including metrics on traffic, errors, and quota usage.

0 commit comments

Comments
 (0)