Refactor credential handling in documentation to clarify automatic sa… #205
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.
Note
Low Risk
Documentation-only changes that adjust example code and behavior description; low risk aside from potential confusion if backend defaults differ from what’s documented.
Overview
Updates the documentation to treat credential capture as the default behavior for Managed Auth logins, removing the previously documented
save_credential_asparameter fromkernel.auth.connections.loginexamples across the Credentials, Hosted UI, Overview, and Programmatic pages.Adds explicit guidance and examples for opting out of credential saving via
save_credentials: falsewhen creating a connection, and adjusts related wording to describe automatic merging/saving of user-provided values on successful login.Written by Cursor Bugbot for commit 585a6d9. This will update automatically on new commits. Configure here.