-
Notifications
You must be signed in to change notification settings - Fork 52
Added documentation for Membership Providers configuration #766
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: main
Are you sure you want to change the base?
Conversation
Added documentation for Membership Providers configuration This will be useful to link to from the release notes of the next DNN version considering this PR dnnsoftware/Dnn.Platform#6638
### Security Recommendations | ||
|
||
1. **Always use Hashed format** in production environments | ||
2. **Upgrade to SHA256** when using DNN 10.2.0 or later for enhanced security |
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.
I would add a note here referencing the steps are documented below
SET UpdatePassword = 1 | ||
``` | ||
|
||
### Changing only the hashing algorithm |
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.
I would be explicit here "Changing from SHA-1 to SHA-256" or similar.
|
||
> 💡You can check the `LastPasswordChangedDate` in the `aspnet_Membership` table to see which users did change their passwords or not after the date of that change. You may use that information to later delete users that may no longer be activivally engaged. Additionally you can wipe the `Password` field if you want to make sure no passwords with the old algorithm are kept (before notifying users about the change). | ||
|
||
> 💡**Is it critical to migrate from Encrypted to Hashed?** |
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.
I think this should be moved above the heading on line 117 to be with the section about changing from Encrypted -> Hashed.
@mitchelsellers adjusted as per your feedback |
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.
I have adjusted the versions as we agreed this would be a v10.2.0 thing
This will be useful to link to from the release notes of the next DNN version considering this PR dnnsoftware/Dnn.Platform#6638