Why is this still marked as Alpha?

[bmontalvo]

Hello, I'm just getting started on working with SCIM 2.0 and I really dig this project. However without PATCH functionality, this project is somewhat unusable for my purposes since I need to support PATCH for user deactivation. I'm curious why no further work is being done on such a useful project. Is it because Microsoft released a competing NuGet (Microsoft.SystemForCrossDomainIdentityManagement ) package? Is there some other library that you could point me towards that provides SCIM functionality in .NET?

Best regards,
Bobby

[chihoyeung]

we currently use this code in production, and as far as PATCH, it's mostly there as I have code that calls the user endpoint with this body:

var patchContent =
@"{
""schemas"": [""urn:ietf:params:scim:api:messages:2.0:PatchOp""],
""Operations"": [{
""op"": ""replace"",
""path"": ""active"",
""value"": ""false""
}]
}";

[bmontalvo]

I got it working! I needed to update the KernelUser in the example to support the properties I was PATCHing (i.e. Active) and AutoMapper did the rest. Killer project, guys! I'm curious why this is marked as Alpha if it is being used in Production?

[dgioulakis]

@bmontalvo I really appreciate your interest in this project and reaching out to us. Unfortunately, we haven't had many contributions to the codebase and due to higher-priority commitments at PowerDMS, we've had to hold off on further Owin.Scim development.

We do, however, see the future in SCIM as more identity providers and cloud vendors add support for it. Personally, I'd love to continue implementing more of the protocol's specification; just haven't had time.