> 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-bridge/jp/migrating-from-keeper-bridge-to-scim-provisioning.md).

# KeeperブリッジからSCIMプロビジョニングへの移行

Keeperブリッジサーバーの廃止からSCIMプロビジョニングへの移行手順

### Keeperブリッジサービスの停止と無効化

Keeperブリッジアプリケーションを閉じ、マシン上のサービスを**停止**してから**無効化**します。

<figure><img src="https://676463934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5iG49m9DpAvlTGuiIxdZ%2Fuploads%2Fgit-blob-63c2ff9356db51d1b7bc428dbf9b22eeec0cc483%2Fimage-ja.png?alt=media" alt=""><figcaption></figcaption></figure>

Keeper管理コンソールからブリッジプロビジョニングを削除します。

<figure><img src="https://676463934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5iG49m9DpAvlTGuiIxdZ%2Fuploads%2Fgit-blob-b80f646aff03587e41df210c7be20db91781a789%2Fimage%20(1)-ja.png?alt=media" alt=""><figcaption></figcaption></figure>

### サブノードのユーザーをすべて最上位のSSOノードへ移動する

ノード構成画面でツリーの最下位レベルまで移動します。

![](https://676463934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5iG49m9DpAvlTGuiIxdZ%2Fuploads%2Fgit-blob-85002bacb052d13c78cb810b95647d501e46c87f%2Funknown%20\(4\).png?alt=media)

サブノードにいるユーザーをすべて、最上位のSSOノードへ移動します。

![](https://676463934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5iG49m9DpAvlTGuiIxdZ%2Fuploads%2Fgit-blob-3b7c79c8dc7da2880e12f35bf30db68104ef64dd%2Funknown%20\(5\).png?alt=media)

#### Keeperコマンダーを使用する

ユーザー数が多い場合、ノード間の移動は負担が大きくなります。 [**Keeperコマンダー**](/keeperpam/commander-cli/overview.md)の利用を推奨します。

* 「Bridge」ノードとそのサブノードから全ユーザーを `action-report` で移動

{% code overflow="wrap" %}

```
action-report --target all --node "Bridge" --recursive --apply-action move --target-node "SSO"
```

{% endcode %}

* 1人以上のユーザーを `enterprise-user` で指定ノードへ移動

```
enterprise-user [user email] [user email] --node "SSO"
```

<figure><img src="https://676463934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5iG49m9DpAvlTGuiIxdZ%2Fuploads%2Fgit-blob-53f2a3d92c6f5985fcb3df60f5398d35cdbcc172%2Funknown%20(6).png?alt=media" alt=""><figcaption></figcaption></figure>

### IdPのSCIMプロビジョニングを設定する

SSOコネクトで利用するアイデンティティプロバイダー (IdP) の選定と、SCIMプロビジョニングの設定手順は、以下の各ドキュメントをご参照ください。<br>

* [クラウドSSOコネクト](/sso-connect-cloud/jp/identity-provider-setup.md)
* [オンプレミスSSOコネクト](/sso-connect-on-prem/jp/identity-provider-setup.md)
* [SCIMプロビジョニング](/enterprise-guide/jp/user-and-team-provisioning/azure-ad-provisioning-scim.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-bridge/jp/migrating-from-keeper-bridge-to-scim-provisioning.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.