# MVP SCIM functionality **URL:** \ **Category:** SCIM\ **Created:** [July 28, 2025, 10:58am UTC](https://devforum.okta.com/t/mvp-scim-functionality/34033 "2025-07-28T10:58:38Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Amrit](https://avatars.discourse-cdn.com/v4/letter/a/d9b06d/32.png) [@Amrit](https://devforum.okta.com/u/Amrit)\ **Post date:** [July 28, 2025, 10:58am UTC](https://devforum.okta.com/t/mvp-scim-functionality/34033/1 "2025-07-28T10:58:38Z")
Hello, We are in the initial stages of building a custom SCIM 2.0 server to integrate with Okta as an Identity Provider. Our goal is to understand if we can adopt an incremental, phased approach to building out our SCIM capabilities, or if the Okta SCIM client requires a fully functional server (supporting all core operations) from day one to work correctly. For example, could we follow a development plan like this? 1. **Phase 1 (Deprovisioning Focus):** Initially, only implement `GET /Users` (for lookups) and `PATCH /Users` (specifically to support deactivation with `active: false`). 2. **Phase 2 (Provisioning):** Later, add support for `POST /Users` to handle user creation. 3. **Phase 3 (Groups, etc.):** Subsequently, add support for `/Groups` and other features. **Our Specific Questions Are:** 1. **Is an incremental approach viable?** Or will the Okta provisioning service encounter critical, non-recoverable errors if, for instance, it attempts to create a user but the `POST /Users` endpoint is not yet implemented? 2. **What is the minimum required set of endpoints** for the Okta SCIM client to function without getting into a persistent error state? For example, must `POST /Users` be available before any users are assigned to the application? 3. What is the recommended best practice from Okta for developing a new SCIM integration? Is there a “minimum viable SCIM server” definition that we should aim for in our first release? We want to ensure we can deliver value iteratively without causing downstream issues in our customers’ Okta tenants. Any guidance or insights from your experience would be greatly appreciated. ---
**Author:** ![ramgan](https://avatars.discourse-cdn.com/v4/letter/r/ba9def/32.png) [@ramgan](https://devforum.okta.com/u/ramgan)\ **Post date:** [July 28, 2025, 1:31pm UTC](https://devforum.okta.com/t/mvp-scim-functionality/34033/2 "2025-07-28T13:31:36Z")
> [@Amrit](#): > > **incremental approach viable?** Or will the Okta provisioning service encounter critical, non-recoverable errors if, for insta `GET /users` is the only mandatory method you need, you could technically release a version accepting **GET** and **PATCH** requests and progressively perform upgrades to your app. You might have to support SCIM compliant filtering in your endpoint even in your first version as Okta tries to locate existing users for any operation. During submission you would select something like this ![Screenshot 2025-07-28 at 9.30.57 AM](https://global.discourse-cdn.com/oktadev/original/2X/4/4fab7793e0a17bf1a0c46832cbef2e379b81cefc.png) Here are couple of blogs about building a SCIM server > **[How to Submit Your System for Cross-domain Identity Management (SCIM)...](https://developer.okta.com/blog/2024/12/30/scim-okta-integration-network)** > > A guide to submitting your user management integration with SCIM to the Okta Integration Network as an added secure feature to offer your enterprise customers. > **[How to Manage User Lifecycle with .NET and SCIM](https://developer.okta.com/blog/2024/02/29/net-scim)** > > Manage your user's lifecycles using .NET, SCIM, and an Identity Provider such as Okta. ---
**Author:** ![Amrit](https://avatars.discourse-cdn.com/v4/letter/a/d9b06d/32.png) [@Amrit](https://devforum.okta.com/u/Amrit)\ **Post date:** [July 28, 2025, 4:08pm UTC](https://devforum.okta.com/t/mvp-scim-functionality/34033/3 "2025-07-28T16:08:51Z")
Hi Ram, thanks for your reply. We enabled SCIM only for deprovisioning and we are receiving PUT as well as POST request. We don’t see any PATCH request. Can you advise on how best to move ahead ? ---
**Author:** ![ramgan](https://avatars.discourse-cdn.com/v4/letter/r/ba9def/32.png) [@ramgan](https://devforum.okta.com/u/ramgan)\ **Post date:** [July 28, 2025, 4:56pm UTC](https://devforum.okta.com/t/mvp-scim-functionality/34033/4 "2025-07-28T16:56:31Z")
> [@Amrit](#): > > We don’t see any PATCH request. Can you advise on how best to move ahead ? What kind of app are you using? An app created using AIW via **Create App Integration** button or using template app (refer [this](https://developer.okta.com/blog/2024/02/29/net-scim#create-a-scim-provisioning-application-in-okta)) What are the steps you are doing to get the PUT/POST requests? What does your provisioning settings look like? ![Screenshot 2025-07-28 at 12.53.23 PM](https://global.discourse-cdn.com/oktadev/original/2X/8/8dc09d2e40cea86ba92ddc42afafde5c4bb50e5e.png) I see a PATCH request during deactivation on my side similar to what is mentioned [here](https://developer.okta.com/blog/2024/02/29/net-scim#delete-a-user). You can create a support ticket if you want to share your org specific details for our engineers to take a closer look. ---
**Author:** ![system](https://global.discourse-cdn.com/oktadev/original/1X/589c4c5f80de422d01f47cee7185a7fb8227835c.png) [@system](https://devforum.okta.com/u/system)\ **Post date:** [August 27, 2025, 4:56pm UTC](https://devforum.okta.com/t/mvp-scim-functionality/34033/5 "2025-08-27T16:56:59Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.