Users
The /Users resource endpoint handles user management operations.
Table 3-1 Using HTTP Methods with the Users Resource Endpoint
HTTP Method | Path | Description |
---|---|---|
GET |
/Users/{id} |
Given the ID of the user, returns the Oracle Identity Manager user, if it exists. |
GET |
/Users?filter={filterName} eq "<username | externalId>"&attributes={comma separated attributes} |
Searching for the user requires a filter. Supported filters are userName and externalId. The accepted operator is eq. Attributes is optional. |
POST |
/Users |
Creates a user in Oracle Identity Manager. Existing Oracle Life Sciences IAMS validations apply while creating the user. |
PUT |
/Users/{id} |
Replaces all the attributes of the user. If an attribute is not specified, the value is removed from the user in Oracle Identity Manager. |
PATCH |
/Users/{id} |
Updates only the specified attributes. |
DELETE* |
/Users/{id} |
To maintain audit history, you cannot delete a user in the Oracle Life Sciences IAMS application. Instead, the account is disabled and all the current roles and groups are revoked for this user account. |
*After a user is deleted, when a new user request is received that matches the deleted (disabled) username in Oracle Identity Manager, the application returns a 303 Redirect response with the location of the disabled user. You can either enable the user at this location or pick a new username and resubmit the request.
If the username in the new user request matches an active user, the application returns a 412 Precondition Failed with username already exists error message.
Parent topic: REST Resource Endpoints