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

# ログイン試行のプロパティ

KCMバージョン2.9.6以降では、複数回連続してログインに失敗した後のユーザーのログイン機能を制限するようにKCMを設定できます。これにより、KCMインスタンスに対する総当たりログイン攻撃をブロックできます。

{% hint style="info" %}
ログインの試行に5回失敗すると、KCMはデフォルトでユーザーのログインを5分間ロックします。
{% endhint %}

ログイン試行の設定を変更するには、以下のプロパティを使用します。

| プロパティ                      | 説明                                                     |
| -------------------------- | ------------------------------------------------------ |
| `ban-max-invalid-attempts` | ユーザーがロックされるまでの無効な試行回数。                                 |
| `ban-address-duration`     | 無効な試行回数の制限に達した後に、ユーザーがロックされる時間（秒単位）。                   |
| `ban-max-addresses`        | KCMが無効な試行回数をチェックするために追跡管理するアドレスの数。 デフォルトは`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 dynamically by asking a question.

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

```
GET https://docs.keeper.io/keeper-connection-manager/jp/advanced-configuration/guacamole.properties/login-attempts-properties.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.