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

# KeeperオンプレミスSSOコネクト

セルフホスト型SAML 2.0連携向けの従来版SSOコネクト

<figure><img src="https://2257682436-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpnnyqlSSLL0TJdycg6le%2Fuploads%2Fgit-blob-d54ee4bdb72d001ef0f713b9effd99e6b26c2dda%2Fsso-connect-onprem.jpg?alt=media" alt=""><figcaption></figcaption></figure>

KeeperオンプレミスSSOコネクトを使用すると、ゼロ知識セキュリティアーキテクチャを活用しつつ、SAML 2.0 IDプロバイダとのシームレスな統合が可能です。

本ガイドでは、Keeper SSOコネクトをパブリッククラウド、プライベートクラウド、オンプレミス環境に展開して、Keeperエンタープライズの強力な機能を使用する方法について解説します。

{% hint style="info" %}
完全なクラウドベースの統合をお求めのお客様は、[KeeperクラウドSSOコネクト](https://docs.keeper.io/sso-connect-cloud/jp/)をご参照ください。

新規のお客様には、KeeperクラウドSSOコネクトの導入をお勧めします。

[**詳細はこちら**](https://docs.keeper.io/sso-connect-cloud/jp/)
{% endhint %}

#### セットアップ (1時間程度)

1. Keeper管理コンソールでSSO統合を設定します。
2. 必要に応じて、プライベートかパブリックのクラウドインスタンスやオンプレミスで、Keeper SSOコネクトサービスをダウンロードし、インストールして設定します。
3. IDプロバイダでKeeperアプリケーションを設定します。

概要とシステム要件の詳細については、後続のページをご覧ください。


---

# 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/readme.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.
