> 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/authentication.md).

# 認証オプション

Keeperコネクションマネージャーの認証メソッドの設定

<figure><img src="https://4041518992-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ7s6LQJaKa1G17O787JG%2Fuploads%2FADvq6PDqYi9xNFotjxQm%2Fimage.png?alt=media&amp;token=943795c9-a84c-4bfb-abbe-59717072e023" alt=""><figcaption></figcaption></figure>

Keeperコネクションマネージャーでは、複数の認証方式に対応しています。それらの認証方式は追加パッケージをインストールすることで有効にできます。

### 認証方式

* [SAML 2.0](/keeper-connection-manager/jp/authentication/authenticating-users-with-saml.md)
* [OpenID Connect](/keeper-connection-manager/jp/authentication/authenticating-users-with-openid-connect.md)
* [LDAP](/keeper-connection-manager/jp/authentication/authenticating-users-with-ldap.md)

### 多要素認証 <a href="#id-.authenticationv2.x-multi-factorauthentication" id="id-.authenticationv2.x-multi-factorauthentication"></a>

Keeperコネクションマネージャーで多要素認証を有効にする場合は、DuoまたはTOTPを使用します。

* [TOTP](/keeper-connection-manager/jp/authentication/using-totp-for-multi-factor-authentication.md)
* [Duo](/keeper-connection-manager/jp/authentication/using-duo-for-multi-factor-authentication.md)


---

# 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/jp/authentication.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.