Replace a permission set.
PUT/v1/catalogs/:catalogId/models/:modelId/permission-sets/:permissionSetId
Every field in the body is authoritative: scopes, users and groups that are not listed are removed from the set. The names accepted here come from the Identities endpoints: getUsers returns the userName values valid in users, and getGroups the name values valid in groups. A username or group name that does not exist in the identity provider is ignored rather than rejected, and the rest of the set is still applied. Read the set back to confirm which principals were granted.
Request
Path Parameters
Identifier of the catalog.
Identifier of the model within the catalog.
Identifier of the permission set.
Header Parameters
- application/json
Body
required
Possible values: non-empty
Display name of the permission set. Not required to be unique within the model.
Possible values: [ctas, discovery, query], >= 1
Operations the listed principals may perform on the model. ctas allows aggregate creation, discovery allows the model to be listed and browsed, query allows queries against it.
Possible values: non-empty
Default value: ``
Usernames granted the listed scopes. A username that does not exist in the identity provider is ignored; see the operation description.
Possible values: non-empty
Default value: ``
Group names granted the listed scopes. A group that does not exist in the identity provider is ignored; see the operation description.
Responses
- 204
- 400
- 401
- 403
- 404
- 500
The permission set has been replaced.
Invalid request for example: Invalid parameters, missing parameters.
Unauthorized. This error will occur if calling user does not have access right for the API.
Forbidden. This error will occur if the user lacks the proper roles or permissions to perform this action.
No permission set with that identifier exists on the given catalog and model.
A server error occurred. Check the logs for more details.