Conversation
The IAM Identity Center section only documented the legacy inline profile form. Lead with the recommended [sso-session] form (botocore 1.29.10+), document sso_registration_scopes, and label the inline form as the legacy non-refreshable configuration with a migration pointer. Refs boto/botocore#3776
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs boto/botocore#3776
Problem
The AWS IAM Identity Center section of the credentials guide only documents the inline profile form.
sso_sessionand[sso-session]aren't mentioned anywhere, even though botocore has supported them since 1.29.10.That's a functional gap: the AWS SDKs and Tools reference calls the
sso-sessionform the recommended SSO token provider configuration, and the inline form the legacy non-refreshable configuration (no automated token refresh, session fixed at eight hours). The guide currently steers readers onto the legacy path without saying so.Change
In
docs/source/guide/credentials.rst:[sso-session]configuration, including a profile + sso-session example.sso_registration_scopes.[sso-session].Validation
develop(:ref:roles unknown to plain docutils at lines 30/110/270 and a short title underline at line 351) — none in the changed region.configparser.