This is a cache of https://docs.okd.io/latest/rest_api/user_and_group_apis/user-user-openshift-io-v1.html. It is a snapshot of the page at 2024-11-26T19:53:27.463+0000.
User [user.openshift.io/v1] - User and group <strong>api</strong>s | <strong>api</strong> reference | OKD 4
  1. Documentation
×

User [user.openshift.io/v1]

Description

Upon log in, every user of the system receives a User and Identity resource. Administrators may directly manipulate the attributes of the users for their own tracking, or set groups via the api. The user name is unique and is chosen based on the value provided by the identity provider - if a user already exists with the incoming name, the user name may have a number appended to it depending on the configuration of the system.

Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).

Type

object

Required

  • groups

Specification

Property Type Description

apiVersion

string

apiVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources

fullName

string

FullName is the full name of user

groups

array (string)

Groups specifies group names this user is a member of. This field is deprecated and will be removed in a future release. Instead, create a Group object containing the name of this User.

identities

array (string)

Identities are the identities associated with this user

kind

string

Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds

metadata

ObjectMeta_v2

metadata is the standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

api endpoints

The following api endpoints are available:

  • /apis/user.openshift.io/v1/users

    • DELETE: delete collection of User

    • GET: list or watch objects of kind User

    • POST: create an User

  • /apis/user.openshift.io/v1/watch/users

    • GET: watch individual changes to a list of User. deprecated: use the 'watch' parameter with a list operation instead.

  • /apis/user.openshift.io/v1/users/{name}

    • DELETE: delete an User

    • GET: read the specified User

    • PATCH: partially update the specified User

    • PUT: replace the specified User

  • /apis/user.openshift.io/v1/watch/users/{name}

    • GET: watch changes to an object of kind User. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.

/apis/user.openshift.io/v1/users

HTTP method

DELETE

Description

delete collection of User

Table 1. Query parameters
Parameter Type Description

dryRun

string

When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
Table 2. HTTP responses
HTTP code Reponse body

200 - OK

Status_v11 schema

401 - Unauthorized

Empty
HTTP method

GET

Description

list or watch objects of kind User

Table 3. HTTP responses
HTTP code Reponse body

200 - OK

UserList schema

401 - Unauthorized

Empty
HTTP method

POST

Description

create an User

Table 4. Query parameters
Parameter Type Description

dryRun

string

When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed

fieldValidation

string

fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
Table 5. Body parameters
Parameter Type Description

body

User schema
Table 6. HTTP responses
HTTP code Reponse body

200 - OK

User schema

201 - Created

User schema

202 - Accepted

User schema

401 - Unauthorized

Empty

/apis/user.openshift.io/v1/watch/users

HTTP method

GET

Description

watch individual changes to a list of User. deprecated: use the 'watch' parameter with a list operation instead.

Table 7. HTTP responses
HTTP code Reponse body

200 - OK

WatchEvent schema

401 - Unauthorized

Empty

/apis/user.openshift.io/v1/users/{name}

Table 8. Global path parameters
Parameter Type Description

name

string

name of the User
HTTP method

DELETE

Description

delete an User

Table 9. Query parameters
Parameter Type Description

dryRun

string

When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
Table 10. HTTP responses
HTTP code Reponse body

200 - OK

Status_v11 schema

202 - Accepted

Status_v11 schema

401 - Unauthorized

Empty
HTTP method

GET

Description

read the specified User

Table 11. HTTP responses
HTTP code Reponse body

200 - OK

User schema

401 - Unauthorized

Empty
HTTP method

PATCH

Description

partially update the specified User

Table 12. Query parameters
Parameter Type Description

dryRun

string

When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed

fieldValidation

string

fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
Table 13. HTTP responses
HTTP code Reponse body

200 - OK

User schema

201 - Created

User schema

401 - Unauthorized

Empty
HTTP method

PUT

Description

replace the specified User

Table 14. Query parameters
Parameter Type Description

dryRun

string

When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed

fieldValidation

string

fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
Table 15. Body parameters
Parameter Type Description

body

User schema
Table 16. HTTP responses
HTTP code Reponse body

200 - OK

User schema

201 - Created

User schema

401 - Unauthorized

Empty

/apis/user.openshift.io/v1/watch/users/{name}

Table 17. Global path parameters
Parameter Type Description

name

string

name of the User
HTTP method

GET

Description

watch changes to an object of kind User. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.

Table 18. HTTP responses
HTTP code Reponse body

200 - OK

WatchEvent schema

401 - Unauthorized

Empty