Verify user authorization in RSSO AdminUser database

Verifies that the user is configured in the AdminUsers database in Remedy Single Sign-On (RSSO). This validates that the user is authorized to perform configuration actions, including adding a tenant, a user, or role, as well as other local user and role management tasks.

When a user attempts to perform a local user or role management task, this call is triggered in the background to verify that the user is authorized to perform the task.

This topic includes the following sections:

Request
Response
Status code and messages
Related topic

Request

HTTP method: POST

URL: https://<hostname>:<port>/rsso/config/isauthorized

Request body properties

Property	Type	Required	Description	Values	Default value
userName	String	Yes	Login ID of the user whose record may or may not exist in AdminUsers table	User-specified	NA
uri	String	No	A request URI for which the user may or may not have access This is currently a placeholder. This field is not used to check if the user is authorized to perform actions in RSSO.	User-specified For example, /config/local/user/add	NA

Example request JSON

{
"userName" : "admin",
"uri" : "/config/local/user/add"
}

Response

If successful, this method verifies that the specified user is included in the RSSO AdminUser database and, therefore, has authorization to perform local user and role management tasks. If the user attempts to perform one of these tasks and is not a member, the user gets a not authorized message.

Response body properties

Property	Description
code	Status code (see Status codes and messages)
msg	Success or error message If successful, the value will be OK.
data	NA

Example response JSON

{
"code":200,
"msg":"OK",
"data":{}
}

{
"code":401,
"msg":"Not authorized",
"data":{}
}

Status code and messages

For more details about HTTP response codes, see HTTP response codes.

HTTP code	Message (msg)	Description
200	OK	Request succeeded The user is authorized to perform the action related to the URI specified in the request.
400	Authentication failed	Authentication failed Causes might be Invalid user Invalid password.
401	Not authorized	Unauthorized The user is not authorized to perform the action related to the URI specified in the request.