# Add SCIM support as service provider

**URL:** https://meta.discourse.org/t/add-scim-support-as-service-provider/328042
**Category:** Feature
**Tags:** sso
**Created:** [September 25, 2024, 8:38am UTC](https://meta.discourse.org/t/add-scim-support-as-service-provider/328042 "2024-09-25T08:38:26Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 25, 2024, 2:42pm UTC](https://meta.discourse.org/t/add-scim-support-as-service-provider/328042/2 "2024-09-25T14:42:53Z")

</div>

It seems odd that their spec uses `/Users` and `/Groups` rather than something like `.well-known/scim/Users`. It seems assured that it will conflict with existing routes on many applications.

I’d be happy to help out with that if you’ve got some budget to spare.

I can imagine that if it were well-written and widely-used (or required by several enterprise customers) that it might become an offical plugin.

I don’t imagine that it would ever become part of core–even Oauth2 is a plugin.

---

_[View the full topic](https://meta.discourse.org/t/add-scim-support-as-service-provider/328042)._