-
Notifications
You must be signed in to change notification settings - Fork 169
Update user and admin docs, prepare for more screenshots #701
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
@kasparsd related to your thoughts on #699, some questions:
I'll update here once you weigh-in on those questions. I'll work on some additional screenshots to note what I added here as captions in this readme update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great! Amazing work.
To answer your questions:
-
IMHO none of the magic-link plugins will work if the two-factor is enabled.
-
I suggest we link to https://wordpress.org/plugins/two-factor-provider-webauthn/ directly because it integrates specifically with the two-factor plugin and does it really well.
|
||
## Setup Instructions | ||
|
||
**Important**: Each user must individually configure their two-factor authentication settings. There are no site-wide settings for this plugin. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe link to the issue where this is being discussed?
1. **Navigate to your profile**: Go to "Users" → "Your Profile" in the WordPress admin | ||
2. **Find Two-Factor Options**: Scroll down to the "Two-Factor Options" section | ||
3. **Choose your methods**: Enable one or more authentication providers (noting a site admin may have hidden one or more so what is available could vary): | ||
- **Authenticator App (TOTP)** - Use apps like Google Authenticator, Authy, or 1Password |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe follow the new order in the settings which have app first followed by backup codes (to ensure they have fallback)?
|
||
= Why doesn't this plugin have site-wide settings? = | ||
|
||
This plugin is designed to work on a per-user basis, allowing each user to choose their preferred authentication methods. This approach provides maximum flexibility and security. Site administrators can still configure 2FA for other users by editing their profiles. For more information, see [issue #437](https://github.com/WordPress/two-factor/issues/437). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we also link to all the available actions/filters in the readme, saying that on larger sites it is recommended to enforce certain requirements via code?
@jeffpaul I would like to merge this for the next release. Would you have time to iterate on it now or can we merge it as is and update later? |
What?
This pull request significantly updates the
readme.txt
file for the Two-Factor Authentication (2FA) plugin, enhancing user guidance and improving the documentation. Key changes include the addition of detailed setup instructions, descriptions of authentication methods, and answers to frequently asked questions (FAQs).Enhanced User Guidance:
readme.txt
, readme.txtL13-R91).readme.txt
, readme.txtL13-R91).Improved Documentation of Authentication Methods:
readme.txt
, readme.txtL13-R91).readme.txt
, readme.txtL13-R91).Added FAQs and Clarifications:
readme.txt
, readme.txtR123-R141).Updated Visual References:
readme.txt
, readme.txtR123-R141).Why?
Closes #699.
How?
Testing Instructions
Screenshots or screencast
Changelog Entry