# SCIM-ondersteuning toevoegen als serviceprovider

**URL:** https://meta.discourse.org/t/add-scim-support-as-service-provider/328042
**Category:** Feature
**Tags:** sso
**Created:** [25 september 2024 om 08:38 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:** 4

<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: [26 september 2024 om 13:52 UTC](https://meta.discourse.org/t/add-scim-support-as-service-provider/328042/4 "2024-09-26T13:52:27Z")

</div>

> [@pbouda](#):
>
> think it’s possible to use any path as prefix for the SCIM endpoints

Ah. That makes sense. I figured that must be the case but didn’t see that in my quick read. I’d take a look at the other authentication plugins as a reference.

Here are official plugins with ‘auth’ in their name

```plaintext
discourse-apple-auth/ discourse-microsoft-auth/
discourse-authentication-validations/ discourse-oauth2-basic/
discourse-auth-no-email/ discourse-vk-auth/
discourse-development-auth/ discourse-wikimedia-auth/

```

Sounds like an interesting project

---

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