# OneLogin SCIM Provisioner → Auth0 SAML connection: deprovision/update fails with "invalid URI" (pipe-delimited id). OneLogin-specific workaround?

**URL:** <https://community.auth0.com/t/onelogin-scim-provisioner-auth0-saml-connection-deprovision-update-fails-with-invalid-uri-pipe-delimited-id-onelogin-specific-workaround/200645>\
**Category:** Get Help\
**Tags:** connection-provisioning-flows, connections\
**Created:** [June 8, 2026, 3:33pm UTC](https://community.auth0.com/t/onelogin-scim-provisioner-auth0-saml-connection-deprovision-update-fails-with-invalid-uri-pipe-delimited-id-onelogin-specific-workaround/200645 "2026-06-08T15:33:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sujit.iwale](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sujit.iwale/32/70854_2.png) [@sujit.iwale](https://community.auth0.com/u/sujit.iwale)\
**Post date:** [June 8, 2026, 3:33pm UTC](https://community.auth0.com/t/onelogin-scim-provisioner-auth0-saml-connection-deprovision-update-fails-with-invalid-uri-pipe-delimited-id-onelogin-specific-workaround/200645/1 "2026-06-08T15:33:00Z")

</div>

We’re integrating OneLogin as our IdP with Auth0 for provisioning over SCIM, and we’re hitting an error during deprovisioning.

Setup

- IdP: OneLogin, using the SCIM Provisioner with SAML (SCIM v2 Enterprise) connector
- Auth0: SAML enterprise connection with Sync user profiles using SCIM = On
- Mapping → “SCIM attribute containing the user ID” = userName (mapped to email)

What works

- CREATE (user.created) succeeds — the user is created in Auth0 and a 201 is returned.

What fails

- Deprovisioning (DELETE) — and updates (PATCH) — fail. OneLogin reports:

Provisioning failed due to an invalid URI:  
“/Users/samlp|astra-onelogin-staging|adam.west@staging.com”

- It looks like Auth0’s CREATE response returns the resource id as the internal user\_id samlp||. OneLogin stores that id and reuses it as  
DELETE /Users/{id}, but the | pipe characters are illegal in a URI path (RFC 3986), so the request never forms a valid URI.

Questions

1. Is there a supported way to have Auth0 return a URL-safe SCIM id (e.g. the userName/email) in the CREATE response, or to URL-encode the user\_id in  
meta.location?
2. Has anyone gotten OneLogin → Auth0 (SAML connection) SCIM to deprovision/update successfully — and if so, what config made it work?
3. For SAML connections, is the pipe-delimited id expected to break SCIM clients that key off id for PATCH/DELETE, and is a fix planned?

Any guidance on getting the full lifecycle (create → update → deprovision) working with OneLogin would be much appreciated.

---

<div class="post-metadata">

**Author:** ![gerald.czifra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gerald.czifra/32/75301_2.png) [@gerald.czifra](https://community.auth0.com/u/gerald.czifra)\
**Post date:** [June 9, 2026, 2:36pm UTC](https://community.auth0.com/t/onelogin-scim-provisioner-auth0-saml-connection-deprovision-update-fails-with-invalid-uri-pipe-delimited-id-onelogin-specific-workaround/200645/3 "2026-06-09T14:36:25Z")

</div>

Hi @sujit.iwale

Welcome to the Auth0 Community!

Thank you for the provided details and context. Please allow me some time to research this matter and I will provide an update with our recommendations in a timely manner.

Best regards,  
Gerald

---

<div class="post-metadata">

**Author:** ![asaf.levy](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/asaf.levy/32/80379_2.png) [@asaf.levy](https://community.auth0.com/u/asaf.levy)\
**Post date:** [August 13, 2026, 1:10pm UTC](https://community.auth0.com/t/onelogin-scim-provisioner-auth0-saml-connection-deprovision-update-fails-with-invalid-uri-pipe-delimited-id-onelogin-specific-workaround/200645/4 "2026-08-13T13:10:56Z")

</div>

We have encountered the same exact issue, and have reached out to both Auth0 support and Onelogin, I’ll try an update if there’s good news..

Auth0 support confirmed that `/Users/{id}` will always be a pipe-delimited string containing the `protocol|connection-name|user-id`

---

<div class="post-metadata">

**Author:** ![asaf.levy](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/asaf.levy/32/80379_2.png) [@asaf.levy](https://community.auth0.com/u/asaf.levy)\
**Post date:** [September 6, 2026, 10:47am UTC](https://community.auth0.com/t/onelogin-scim-provisioner-auth0-saml-connection-deprovision-update-fails-with-invalid-uri-pipe-delimited-id-onelogin-specific-workaround/200645/5 "2026-09-06T10:47:52Z")

</div>

All cased closed in unresolved status,  
Auth0 Enterprise support couldn’t find a resolution, and Onelogin choose to ignore the issue (for free demo account)
