AWS cli documentation change
Summary
Updated AWS CLI version reference from 2.35.16 to 2.35.19 and added documentation for 'advertisedScopeMapping' parameter in harness configuration
Security assessment
Documents OAuth scope mapping feature to prevent scope mismatches in authentication headers, improving security metadata accuracy. No indication of vulnerability fix.
Diff
diff --git a/cli/latest/reference/bedrock-agentcore-control/get-harness.md b/cli/latest/reference/bedrock-agentcore-control/get-harness.md index 9ff6e3d49..ba7262ed3 100644 --- a//cli/latest/reference/bedrock-agentcore-control/get-harness.md +++ b//cli/latest/reference/bedrock-agentcore-control/get-harness.md @@ -15 +15 @@ - * [AWS CLI 2.35.16 Command Reference](../../index.html) » + * [AWS CLI 2.35.19 Command Reference](../../index.html) » @@ -1333,0 +1334,31 @@ harness -> (structure) +>>> +>>> advertisedScopeMapping -> (map) +>>> +>>>> A map that associates each scope in `allowedScopes` with a corresponding advertised scope value. The advertised scope appears in OAuth protected resource metadata and `WWW-Authenticate` response headers. Use this parameter when the scope that clients request from your identity provider differs from the scope in the validated token. Each key is a scope from `allowedScopes` that the service uses for token validation. Each value is the corresponding scope that the service advertises to clients. Scopes without a mapping entry appear unchanged to clients. +>>>> +>>>> Constraints: +>>>> +>>>> * min: `1` +>>>> * max: `50` +>>>> + +>>>> +>>>> key -> (string) +>>>> +>>>>> Constraints: +>>>>> +>>>>> * min: `1` +>>>>> * max: `255` +>>>>> * pattern: `[\x21\x23-\x5B\x5D-\x7E]+` +>>>>> + +>>>> +>>>> value -> (string) +>>>> +>>>>> Constraints: +>>>>> +>>>>> * min: `1` +>>>>> * max: `255` +>>>>> * pattern: `[\x21\x23-\x5B\x5D-\x7E]+` +>>>>> + @@ -1903 +1934 @@ harness -> (structure) - * [AWS CLI 2.35.16 Command Reference](../../index.html) » + * [AWS CLI 2.35.19 Command Reference](../../index.html) »