# KeeperChat Client Release 4.0.0

## Features and Improvements

* **Login V3 Enhanced Enterprise** **Authentication Flow -** Keeper has launched a new authentication flow for our customers with Enterprise plans that simplifies deployment and usability while enhancing security.
  * If Keeper recognizes an end user’s email domain as an SSO-enabled Enterprise, the user will be automatically routed to their identity provider instead of having to type in the Enterprise Domain string.
  * For Master Password users, if a device is recognized, and 2FA is activated, the user will receive a prompt prior to typing in their Master Password.
  * Keeper Push, Keeper’s proprietary notification-based device approval system, simplifies the device approval process without compromising security. Keeper will now support 2FA code entry from a TOTP or text message or push notification to an existing, recognized device.
  * More information is available here:\
    [Login API](/enterprise-guide/jp/login-api.md)

## Bug Fixes

* CC-1733: DUO-push setup in 2FA
* CC-1708: Self-destruct feature after 5 invalid password attempts


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.keeper.io/release-notes/jp/desktop/keeperchat/norirsu/keeperchat-client-release-4.0.0.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.