Unassign Role
Added by IBM contributorIBM | Edited by Claudia R Elbourn on June 15, 2015
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

The API caller must have a role that is sufficient to unassign the specified role from the subscriber.

Table 1. API details
Method
Resource address
Operation header
POST
/service/authorization/unassignRole?loginName=<loginName>&role=<validRole>
None.


URL parameters


Provide the following parameters.

Table 2. Parameters
Parameter
Required
Description
loginName
Yes
The email address of the subscriber, for example jdoe@example.com
role
Yes
A valid role.

On success, the HTTP response body is empty. On failure, an error code and error message is returned. For a list of common HTTP status codes that are returned for API calls, see HTTP status codes.

Parent topic: Authorization services
Input
Method URI Description
POST /api/bss/service/authorization/unassignRole Remove a role from a subscriber.
The API caller must have a role that is sufficient to assign the specified role to the subscriber.
Content Type: text/plain
Name Type Optional Description
loginName
string No The email address of the subscriber, for example jdoe@example.com
role
string No A valid role
Output
Code Description
401
Unauthorized. Returned when no authenticated user or no userid, email, or key parameter are provided on the request.