Update opt-in mfa requirement docs #346
Merged
Conversation
This file contains 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
Currently the docs outline that the rubygems_mfa_required will require owners to enter an OTP for all privileged operations. In actuality, rubygems_mfa_required will require owners to have just to have MFA enabled (and not specifically at the ui_and_api level).
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.
From rubygems/rubygems.org#4264 (comment)
Currently the docs outline that the
rubygems_mfa_requiredflag will require owners to enter an OTP for all privileged operations (push, yank, owner add and remove). In actuality,rubygems_mfa_requiredwill require owners to have just to have MFA enabled (and not specifically at theui_and_apilevel for the CI/CD case).