Otp Manager

Securely stores your OTP secrets in Chrome's storage and log in to your OTP-protected accounts with just two clicks.
All secrets are stored using encryption and the Web Credential Management API to keep your data safe.

Usage:
Adding a new OTP secret:

1) click the OTP-Manager extension icon
2) click the "Add new" button and follow the instructions

Logging in to an OTP-protected account:
1) When prompted to enter a OTP code, click the OTP-Manager extension icon
2) Select OTP Manager from the list of available credentials
3) For some websites, you may need to click into the OTP token field before clicking the extension icon.

Security:
How are my secrets stored?
On first launch, OTP Manager generates a AES-GCM key and stores it in the extension's storage. This key is used to encrypt your secrets before they are stored on the page itself using the Web Credential API. The key is never stored in plaintext, and is only accessible to the extension itself when the user invokes the extension and selects the identity.

How are my secrets transmitted?
When the user invokes the extension to generate a OTP token, the extension request the encrypted secret from the page. To fulfill this request, the user has to confirm by selecting the OTP Manager identity from the list of available credentials. Then, the extension decrypts the secret and generates the OTP token, which is then sent back to the page. None of your secrets are sent to any third party servers, and the extension only communicates with the page itself.

License
This project is licensed under the MIT License - see the LICENSE file for details

Contribution and source:
https://github.com/MatteoValentini-AT/OTP-Manager