elasticsearch/docs/reference/rest-api/security/enable-user-profile.asciidoc
James Rodewig 255c9a7f95
[DOCS] Move x-pack docs to docs/reference dir (#99209)
**Problem:**
For historical reasons, source files for the Elasticsearch Guide's security, watcher, and Logstash API docs are housed in the `x-pack/docs` directory. This can confuse new contributors who expect Elasticsearch Guide docs to be located in `docs/reference`. 

**Solution:**
- Move the security, watcher, and Logstash API doc source files to the `docs/reference` directory
- Update doc snippet tests to use security

Rel: https://github.com/elastic/platform-docs-team/issues/208
2023-09-12 14:53:41 -04:00

58 lines
1.8 KiB
Text
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

[role="xpack"]
[[security-api-enable-user-profile]]
=== Enable user profile API
++++
<titleabbrev>Enable user profile</titleabbrev>
++++
NOTE: The user profile feature is designed only for use by {kib} and
Elastics {observability}, {ents}, and {elastic-sec} 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.
Enables a user profile so it's visible in
<<security-api-suggest-user-profile,user profile searches>>.
[[security-api-enable-user-profile-request]]
==== {api-request-title}
`POST /_security/profile/<uid>/_enable`
`PUT /_security/profile/<uid>/_enable`
[[security-api-enable-user-profile-prereqs]]
==== {api-prereq-title}
To use this API, you must have the `manage_user_profile` cluster privilege.
[[security-api-enable-user-profile-desc]]
==== {api-description-title}
When you <<security-api-activate-user-profile,activate a user profile>>, it's
automatically enabled and visible in user profile searches. If you later
<<security-api-disable-user-profile,disable the user profile>>, you can use the
enable user profile API to make the profile visible in these searches again.
[[security-api-enable-user-profile-path-params]]
==== {api-path-parms-title}
`<uid>`::
(Required, string) Unique identifier for the user profile.
[[security-api-enable-user-profile-query-params]]
==== {api-query-parms-title}
include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=refresh]
[[security-api-enable-user-profile-example]]
==== {api-examples-title}
The following request enables the user profile for a `uid` matching
`u_79HkWkwmnBH5gqFKwoxggWPjEBOur1zLPXQPEl1VBW0_0`:
[source,console]
----
POST /_security/profile/u_79HkWkwmnBH5gqFKwoxggWPjEBOur1zLPXQPEl1VBW0_0/_enable
----
// TEST[setup:user_profiles]