POST /api/v1/iam/resource-sets/{resourceSetIdOrLabel}/bindings
Creates a binding for the resource set, custom role, and members (users or groups)
Note: If you use a custom role with permissions that don't apply to the resources in the resource set, it doesn't affect the admin role. For example, the
okta.users.userprofile.managepermission gives the admin no privileges if it's granted to a resource set that only includeshttps://{yourOktaDomain}/api/v1/groups/{targetGroupId}resources. If you want the admin to be able to manage the users within the group, the resource set must include the correspondinghttps://{yourOktaDomain}/api/v1/groups/{targetGroupId}/usersresource.
Servers
- https://{yourOktaDomain}
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
resourceSetIdOrLabel |
String | Yes |
|
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
members[] |
Array | No |
URLs to user and/or group instances that are assigned to the role |
role |
String | No |
Unique key for the role |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.