Get user profiles API

Get user profiles API

New API reference

For the most up-to-date API details, refer to Security APIs.

The user profile feature is designed only for use by Kibana and Elastic’s Observability, Enterprise Search, and Elastic Security solutions. Individual users and external applications should not call this API directly. Elastic reserves the right to change or remove this feature in future releases without prior notice.

Retrieves user profiles using a list of unique profile ID.

Request

GET /_security/profile/<uid>

Prerequisites

To use this API, you must have at least the read_security cluster privilege (or a greater privilege such as manage_user_profile or manage_security).

Description

The get user profile API returns the user profile document matching a specified uid, which is generated when activating a user profile.

Path parameters

uid

(Required, string) The unique identifier for the user profile. You can specify multiple IDs as a comma-separated list.

Query parameters

data

(Optional, string) Comma-separated list of filters for the data field of the profile document. To return all content, use data=*. To return a subset of content, use data=<key> to retrieve the content nested under the specified <key>. Defaults to returning no content.

Response body

A successful call returns the JSON representation of the user profile and its internal versioning numbers. The API returns an empty object if no profile document is found for the provided uid. The content of the data field is not returned by default to avoid deserializing a potential large payload.

Examples

  1. resp = client.security.get_user_profile(
  2.     uid="u_79HkWkwmnBH5gqFKwoxggWPjEBOur1zLPXQPEl1VBW0_0",
  3. )
  4. print(resp)
  1. const response = await client.security.getUserProfile({
  2.   uid: "u_79HkWkwmnBH5gqFKwoxggWPjEBOur1zLPXQPEl1VBW0_0",
  3. });
  4. console.log(response);
  1. GET /_security/profile/u_79HkWkwmnBH5gqFKwoxggWPjEBOur1zLPXQPEl1VBW0_0

The API returns the following response for a uid matching u_79HkWkwmnBH5gqFKwoxggWPjEBOur1zLPXQPEl1VBW0_0:

  1. {
  2.   "profiles": [
  3.     {
  4.       "uid": "u_79HkWkwmnBH5gqFKwoxggWPjEBOur1zLPXQPEl1VBW0_0",
  5.       "enabled": true,
  6.       "last_synchronized": 1642650651037,
  7.       "user": {
  8.         "username": "jacknich",
  9.         "roles": [
  10.           "admin", "other_role1"
  11.         ],
  12.         "realm_name": "native",
  13.         "full_name": "Jack Nicholson",
  14.         "email": "jacknich@example.com"
  15.       },
  16.       "labels": {
  17.         "direction": "north"
  18.       },
  19.       "data": {}, 
  20.       "_doc": {
  21.         "_primary_term": 88,
  22.         "_seq_no": 66
  23.       }
  24.     }
  25.   ]
  26. }

No content is returned in the data field by default.

The following request retrieves a subset of data that’s nested under the key app1, along with the user’s profile:

  1. resp = client.security.get_user_profile(
  2.     uid="u_79HkWkwmnBH5gqFKwoxggWPjEBOur1zLPXQPEl1VBW0_0",
  3.     data="app1.key1",
  4. )
  5. print(resp)
  1. const response = await client.security.getUserProfile({
  2.   uid: "u_79HkWkwmnBH5gqFKwoxggWPjEBOur1zLPXQPEl1VBW0_0",
  3.   data: "app1.key1",
  4. });
  5. console.log(response);
  1. GET /_security/profile/u_79HkWkwmnBH5gqFKwoxggWPjEBOur1zLPXQPEl1VBW0_0?data=app1.key1
  1. {
  2.   "profiles": [
  3.     {
  4.       "uid": "u_79HkWkwmnBH5gqFKwoxggWPjEBOur1zLPXQPEl1VBW0_0",
  5.       "enabled": true,
  6.       "last_synchronized": 1642650651037,
  7.       "user": {
  8.         "username": "jacknich",
  9.         "roles": [
  10.           "admin", "other_role1"
  11.         ],
  12.         "realm_name": "native",
  13.         "full_name": "Jack Nicholson",
  14.         "email": "jacknich@example.com"
  15.       },
  16.       "labels": {
  17.         "direction": "north"
  18.       },
  19.       "data": {
  20.         "app1": {
  21.           "key1": "value1"
  22.         }
  23.       },
  24.       "_doc": {
  25.         "_primary_term": 88,
  26.         "_seq_no": 66
  27.       }
  28.     }
  29.   ]
  30. }

If there has been any errors when retrieving the user profiles, they are returned in the errors field:

  1. {
  2.   "profiles": [],
  3.   "errors": {
  4.     "count": 1,
  5.     "details": {
  6.        "u_FmxQt3gr1BBH5wpnz9HkouPj3Q710XkOgg1PWkwLPBW_5": {
  7.          "type": "resource_not_found_exception",
  8.          "reason": "profile document not found"
  9.        }
  10.     }
  11.   }
  12. }