- URL:
- https://<root>/security/users/getEnterpriseUser
- Methods:
GET- Version Introduced:
- 10.3.1
Access requirements
Required privileges
The Portal Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.
Tokens
This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Portal Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.
Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generate operation in the Portal Directory API. For security reasons, all POST requests made to the Portal Administrator API must include a token in the request body.
Description
The get operation returns the description, full name, and email address for a single user in the enterprise identity (user) store configured with the portal. The username parameter is used to specify the enterprise user name. If the user does not exist, an error is returned.
Request parameters
| Parameter | Details |
|---|---|
| User name of the enterprise account. For Windows Active Directory users, this can be either Example: Example |
| The response format. The default value is Values: |
Example usage
The following is a sample POST request URL for the get operation:
POST /<context>/portaladmin/security/users/getEnterpriseUser HTTP/1.1
Host: organization.example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []
username=jdoe&f=jsonJSON Response example
{
"username": "john",
"fullname": "John Doe",
"description": "cn=John Doe,ou=users,ou=ags,dc=domain",
"email": "john_doe@email.com"
}