Creating Permission Set
- Print
- PDF
Creating Permission Set
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
You can create a Permission Set.
Requests
- POST /permission-sets
Request bodies
{
"permissionSetName":"String",
"description":"String",
"systemManagedPolicyIds" : [
"String"
],
"userCreatedPolicyNames" : [
"String"
]
}
Parameters | Required | Type | Description | Restrictions |
---|---|---|---|---|
permissionSetName | Y | String | Permission set name | Must only include uppercase and lowercase English letters, numbers, hyphens (-) and underscores (_) and start with an English letter or a number (2-30 bytes) |
description | Y | String | Permission set description | |
systemManagedPolicyIds | Y | Array | System-managed policy IDs | |
userCreatedPolicyNames | Y | Array | Names of user-defined policies |
Responses
Response bodies
{
"id":"String",
"nrn":"String",
"success": "boolean"
}
Parameters | Type | Description | Restrictions |
---|---|---|---|
id | String | Permission Set ID | |
nrn | String | Permission Set nrn | |
success | oolean | Whether it is a success | |
message | String | Error message indicating a failure |
Errors
Errors that may occur while using this action are listed below. For the error response format, see ErrorResponse.
For more information about common errors, see the NAVER Cloud Platform API.
HTTP status code | Error code | Error message |
---|---|---|
400 | 400 | Invalid request |
400 | 9070 | Permission Set with the same name already exists. |
400 | 9071 | At least one policy must be selected. |
400 | 9072 | System-managed policy does not exist. |
Was this article helpful?