> 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/keeper-connection-manager/advanced-configuration/guacamole.properties/login-attempts-properties.md).

# Login Attempts Properties

As of KCM version 2.9.6, KCM can be configured to limit a user's ability to login after multiple consecutive failed login attempts. This blocks brute-force login attacks on KCM instances.

{% hint style="info" %}
By default KCM will lock a user out of logging in for 5 minutes after 5 failed attempts
{% endhint %}

Use the following properties to change the login attempt settings

| Property                   | Description                                                                                        |
| -------------------------- | -------------------------------------------------------------------------------------------------- |
| `ban-max-invalid-attempts` | The number of invalid attempts before a user is locked out                                         |
| `ban-address-duration`     | The amount of time in seconds a user is locked out for after hitting the invalid attempts limit    |
| `ban-max-addresses`        | The number of addresses that KCM will track to check for invalid attempts.  Defaults to `10485760` |


---

# 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/keeper-connection-manager/advanced-configuration/guacamole.properties/login-attempts-properties.md?ask=<question>&goal=<user_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.