> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/jp/browser-extensions/browser-extension/older/browser-extension-version-12.5.2.md). # Browser Extension Version 12.5.2 Released on August 29th, 2019 ## Enhancements & Benefits This release encompasses new two-factor authentication functionality and a feature improvement along with bug fixes. Below you can find the summary of these items and their benefits. * Two-factor Authentication - This release adds new two-factor authentication functionality to our existing list of capabilities. The new method using TOTP (Time-based One-time Password) adds tokens to records which are unique time-based multi-digit codes commonly used by websites and apps for two factor authentication and makes the capability available across the Chrome Web Store, Mozilla Add-ons and Windows Store. TOTP covers the following functionality: * Protects Two-Factor Codes in an encrypted vault record * Prevents lost access to a Two-Factor Code due to continuous backup * Synchronize Two-Factor Codes to multiple devices and computers * Sharing of Two-Factor Code among individual users & teams * Autofill Two-Factor Codes on most browsers * Emergency Access to your vault * Account Transfer of a user’s vault with Two-Factor codes to admin when off-boarding * Free trial users are restricted to 2 TOTP-enabled records ![TOTP - Chrome Browser Extension Example](https://lh4.googleusercontent.com/Uw2Ojckg7a6pG5uxeUwnCrBQUzX-1FkCBvOAfLnwb_j3L7j016mDZQ3MrgPZFIfiyLv8E0aYgYTEURERO76gjmrVkgEYgIHXtT8Jz0VRCDkU_dUYnV_a3pZhBXwvFz3f2nPmr_xZ) * Changing a "Password Attach Save" to "Submit Button" - This feature improvement allows for the save password button to be attached to the save button in the confirmation screen as well as the submit button on the change password form of the site. This allows the user to skip the confirmation screen going forward. ## Bug Fixes: * Fix for Autofill issue filling out the UN/Pass on the wrong url * Fix for an issue which caused password changes to save the 2 FA to be saved as a custom field * Fix for clickjacking vulnerability * A multitude of record "lock" issues * Adding auto-submit restrictions from vault * A fix for a bug which caused custom field changes to not be published on incremental syncs --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.keeper.io/release-notes/jp/browser-extensions/browser-extension/older/browser-extension-version-12.5.2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.