scim2 | SCIM 2.0 SDK for Java | SDK library

I am trying to figure out if the following behavior is the expected. In my case, I am logged in as a user with username: testuser

I make a PATCH request from my Blazor SPA to the following URL https://myidentityserver/scim2/Me. This is the location the WSO2 IS is located.

The PATCH request,containing a password change and some other patched info,completes successfully and Status Code:200 OK is returned.

Immediately after the aforementioned PATCH request, a call to https://myidentityserver/oauth2/token is made and Status Code: 400 is returned containing the grant_type: refresh_token, client_id: myid, refresh_token:xxxxxx, meaning that the token is invalid.

In my understanding this is the expected behavior as the information that were present in the token have now been altered due to the PATCH and token should be invalidated.

WSO IS version: 5.11.0

I have a secondary userstore (JDBC) created in wso2 IS 5.11.0. 2 roles are added under the userstore. I am using the below SCIM 2.0 api to get the roles. https://{IS_IP}:(PORT}/t/carbon.super/scim2/Roles, but only the roles created under primary user store is listed in the response.

Under the claims list -> http://wso2.org/claims -> Role -> Mapped attributes, I have added the secondary user store to the list. still not getting the response.

Is there any other configuration to be done to get it via scim api?

We are trying to use the Mobile Number verification on Mobile number update with WSO2 Identity Server (v5.11.0) as per this guide, while the SMS OTP is being sent, it is being sent to the old mobile number.

Example: User with mobile number 111111

We are sending the request to the SCIM2.0 API https://hostname/scim2/Me to update the mobile number with the following request:

I just want to use SCIM 2.0 REST APIs that per this guide are out of the box from 5.4.0 version of WSO2IS. I'm using WSO2 IS 5.7.

When I GET /scim2/Me with admin user (HTTP basic authentication), I get a 200 OK response, but when I try to call this API with a different user, I get the following HTTP response:

I used "https://localhost:9443/t/carbon.super/scim2/Bulk" to upload bulk users to WSO2IS. How to add organization,email and mobileno to following data set.

Here is my data object.

I am trying to add user to a tenant. For that I did the following:

1. Created tenant in WSO2 instance
2. Generated access token based on client key and secret for the tenant service provider
3. Use generated token to execute endpoint https://localhost:9443/t/carbon.super/{tenantId}/api/server/v1/scims2/Users, where tenantId is id of the tenant.

After executing the endpoint, I am getting error 401 Unauthorized. Any ideas what am I doing wrong?

I am not sure if it's relevant, but I noticed that when I generate access token from main WSO2 instance (not tenant), I get these scopes

I am trying to create Azure AD provisioning for our Saas product (using scim2). I want multiple customers to be able to connect with their Azure AD tenant.

Microsoft has reference code here: https://github.com/AzureAD/SCIMReferenceCode

However, that is setup to only allow one tenant and also to not use the "secret token" that you set up in azure ad. Even tho the comment specifically states the secret token should not be left empty for production.

Here is the important piece of code from the reference project

I'm calling SCIM2 REST service to get user information based on ID but it doesn't return all user data.when I call https://localhost:9444/scim2/Users/8f9d1e34-c340-4ebe-af11-fa0c4575f676 passing username and password (BASIC) I get this payload:

I created an Application Registration on our Azure AD.

I then use the application registration id to create "Enterprise Application" in our customers' AD's. It goes like this

1. Their admin sign into our system and clicks connect AD
2. We send a challenge (OpenId Connect) that allows them to sign into their microsoft account.
3. This creates our application under "Enterprise Applications" in their AD and it then workes fine with SSO

So far so good. But now we want to add the next logical step with Provisioning with Scim v2 however if I on a customer/test AD browse to our app under Enterprise Application and then click Provisioning I see the following

There is no way to hook up provisioning no matter if I support Scim2 as required. Why is this? Does our app need to be in the gallery for this to work?

I noticed I can go to Enterprise Applications > New application > Non-gallery application and create a new application. This will then work with provisioning. But then our customers would need two apps, one from our app registration that does SSO and one more for provisioning. I would like one app to do both.