![]() Currently it is missing the possibility of editing the name “Authenticator app” or adding a note in the central column (I assure, there is a “description” column!). Note: the above user-interface is not very well designed. Remember to press OK for confirming the entry in KeePass and save the updated KeePass database file. ![]() If the code is recognized, a new “Authenticator app” row will appear among the other sign-in methods. Go back to Microsoft account setup and press Next. They continue to change every 30 seconds. KeePass immediately starts generating OTP values. In KeepPass, right click on the entry where you want to store the code, select “Edit entry (quick)” OTP Generator Setting…Ĭopy the value into the field “Shared secret”. Copy it, pressing the small icon on the right. This is the information needed by TOTP protocol to work. Now the website shows the very key-information we need to setup into the multi-factor-authentication application: the Secret Key. But KeePass runs on a computer, and it is not able to scan it. Normally, at this step, you should scan the QR code with your mobile phone app. The wizard suggests using Microsoft Authenticator. With a work-account, login to and select Security Info. The following step-by-step guide shows how to add KeePass as an authenticator-app. More, availability of keepass-third-party plugins help the embarking but even the “raw” KeePass, starting from the last version (2.51), can be easily used. KeePass, the well-known password manager, ships with a built-in support for TOTP protocol, making it good candidate for using in the MFA process. It just needs to implement the TOTP protocol. However, it is also possible to setup a third-party authenticator application for MFA. Microsoft work-accounts / Azure AD easily integrate with Microsoft Authenticator for Multi-Factor Authentication. ![]() Using KeePass as MFA sign-in method with Microsoft work-accounts
0 Comments
Leave a Reply. |