# PingFederate SCIM directory sync

<!-- Generated by scripts/generate.ts. Do not edit. -->

Connect PingFederate's SCIM provisioning to this app with the URL and token from this setup, choose what it sends and assign the people to sync.

:::caution[Verification]
Not yet verified on a real PingFederate tenant. It was written from the public PingFederate documentation, so labels in the admin console may differ slightly.
:::

The values in braces, such as `{scim_base_url}`, are specific to your connection. The setup link from the application you are connecting shows them with a copy button. The same steps appear there.

## Steps

<ol class="idp-steps">

<li class="idp-step">

<a id="app"></a>

### Open the app's provisioning settings

In the admin console of PingFederate, open the app you created for single sign-on, or create one, and go to its SCIM provisioning settings. PingFederate may call this an outbound provisioning or SCIM connector.

:::caution[Labels not confirmed in step 1]
Written generically from the protocol specifications; no public PingFederate admin page was checked for the console's own labels and menu paths.
:::

</li>

<li class="idp-step">

<a id="base-url"></a>

### Enter the SCIM base URL

Paste `{scim_base_url}` into the SCIM base URL field, which may be labelled SCIM endpoint, tenant URL or connector URL.

<div class="setup-values">

Paste into PingFederate:

- SCIM base URL: `{scim_base_url}`

</div>

</li>

<li class="idp-step">

<a id="token"></a>

### Enter the bearer token

Choose bearer token authentication (it may be called OAuth bearer token or HTTP header) and paste `{scim_token}`. The token is shown once in this setup; generate a new one here if you lose it.

<div class="setup-values">

Paste into PingFederate:

- SCIM bearer token: `{scim_token}`

</div>

Fixes: [`scim_token_invalid`](/errors/scim_token_invalid/)

</li>

<li class="idp-step">

<a id="test"></a>

### Test and save

If PingFederate has a connection test for provisioning, run it, then save the settings.

Fixes: [`first_scim_request_pending`](/errors/first_scim_request_pending/)

</li>

<li class="idp-step">

<a id="actions"></a>

### Choose what PingFederate sends

Turn on creating users, updating user attributes and deactivating users. Turn on group push too if you want groups synced.

Fixes: [`scim_user_out_of_domain`](/errors/scim_user_out_of_domain/)

</li>

<li class="idp-step">

<a id="mapping"></a>

### Check the attribute mappings

Map userName to each user's email address or login, and send name.givenName, name.familyName, emails and active. Keep the default mappings for anything else.

</li>

<li class="idp-step">

<a id="assign"></a>

### Assign people and groups

Assign the people or groups to sync to the app. Only assigned people are sent.

</li>

<li class="idp-step">

<a id="start"></a>

### Start provisioning

Turn provisioning on or start the first sync in PingFederate, then check in this setup that the first users arrived.

</li>

</ol>

## Sources

- [RFC 7644: System for Cross-domain Identity Management: Protocol](https://www.rfc-editor.org/rfc/rfc7644), read on 2026-10-29
- [RFC 7643: System for Cross-domain Identity Management: Core Schema](https://www.rfc-editor.org/rfc/rfc7643), read on 2026-10-29
