Closed mikeshootzz closed 1 month ago
Hi, Here is a guide that recommends how to go about using undocumented APIs. https://kasmweb.atlassian.net/servicedesk/customer/portal/3/article/10682377
Maybe this will help. In short, use dev tools to see what the browser is sending when doing the workflow manually. Then slightly adjust the call to work with your API keys
THANK YOU! I've been trying this for days now. This is what worked for me:
Endpoint: /api/public/add_sso_mapping_group
Request body:
{
"api_key": "{{api_key}}",
"api_key_secret": "{{api_key_secret}}",
"target_sso_mapping": {
"group_id": "68d557ac4cac42cca9f31c7c853de0f3",
"sso_id": "d382a9f8-0548-45b5-970e-2f4a14f317e3",
"sso_group_attributes": "/All Users",
"apply_to_all_users": false
}
}
I want to create a group and give it an OIDC mapper using the API. I managed to create a group using the
/api/public/create_group
endpoint (which btw isn't mentioned in the documentation btw, had to figure it out by myself). I used the following request body for this:I looked at my existing group with an OIDC mapper using the
/api/public/get_groups
endpoint, this returned the following:My intuition told me to just add the group mappings to the create group request JSON, but this doesn't work. I also tried using the update group endpoint but with without any luck either. This is what I tried:
Can anyone help me? Thanks!