Closed hauntingEcho closed 3 weeks ago
Quoting the SCIM 2.0 Spec:
SCIM defines three endpoints to facilitate discovery of SCIM service provider features and schema that MAY be retrieved using HTTP GET:
/ServiceProviderConfig /Schemas /ResourceTypes
As of Identity Server 5.9.0, it supports only ResourceTypes
ServiceProviderConfig
endpoints not the Schemas
endpoint.
When a SCIM client like user-portal wants to dynamically discover and adjust to the capability of the SCIM Service Provider(IDP), its needed these endpoint and specially the Schemas
endpoint, since it defines what are the attributes that IDP support and what are the data-types of it it.
Endpoint has been introduced with: wso2/charon#254 & wso2-extensions/identity-inbound-provisioning-scim2#200
User-Schema Impl has been introduced with: wso2/charon#260 & wso2-extensions/identity-inbound-provisioning-scim2#212
Support for user schema from the schema endpoint is implemented with https://github.com/wso2/product-is/issues/6814
Other functionalities like schemas for user extensions, groups needed to be done as further improvements.
This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!
per RFC 7644 section 4:
as of WSO2IS 5.6.0 with WUM update 1557362049847, starting a fresh instance and executing:
curl --user admin:admin -k https://localhost:9443/scim2/Schemas
returns the response:<html><body>No service was found.</body></html>
. This is also the behavior when using the URI of any particular schema, e.g.:curl --user admin:admin -k https://localhost:9443/scim2/Schemas/urn:ietf:params:scim:schemas:core:2.0:User
Subtask