> 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/sso-connect-on-prem/jp/identity-provider-setup.md).

# IDプロバイダの設定

お客様の環境内のサーバーにKeeper SSOコネクトをインストールしたら、以下の手順でIDプロバイダにSAML 2.0認証を設定します。

Keeper SSOコネクトは、あらゆるSAML 2.0準拠のIDプロバイダと統合できます。 いくつかの一般的なプラットフォームに関する手順を以降のページに記載します。

* Azure
* Okta
* Google Workspace
* Microsoft AD FS
* Ping Identity
* OneLogin
* JumpCloud
* RSA SecurID Access
* F5
* Centrify
* AWS SSO

ご利用のIDプロバイダがこちらに記載されていなくても大丈夫です。 Keeperは、すべてのSAML 2.0準拠のSSO IDプロバイダに対応しています。 上記のリストにある同様のプロバイダの上記と同様のプロバイダの手順を参考にしてください。設定の流れはほぼ同じになります。

ご利用のIDプロバイダの設定ガイドを作成された場合は、ぜひ共有をお願いします。こちらに掲載させていただきます。


---

# 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/sso-connect-on-prem/jp/identity-provider-setup.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.