-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
feat(Core/Authserver): TOTP rewrite #5620
Conversation
Need #5518 before |
What is totp? |
WarheadCore/Warhead@421164
Co-authored-by: Kitzunu <[email protected]>
Ready to test |
Thanks, @Winfidonarleyan ill test this later today. |
This looks good. The conversion of existing secrets worked without any problems. removing and setting new 2fa worked great. |
Thanks for tesing, can merge? |
@Winfidonarleyan @locus313 what's the status of this? can it be merged? |
yeah, think this can be merged |
#5518 is already merged as WInfi pointed out, let's go with this one. 🐱 |
Let's go merge |
Changes Proposed:
Issues Addressed:
Tests Performed:
How to Test the Changes:
account
Target Branch(es):
How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as [WAITING TO BE TESTED].
You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
REMEMBER: when testing a PR that changes something generic (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but especially check that the PR does not cause any regression (i.e. introducing new bugs).
For example: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but we should test Y and Z as well.