Este conteúdo não está disponível no idioma selecionado.

Chapter 5. 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

5.1. Specification

PropertyTypeDescription

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

5.2. 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.

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

HTTP method
DELETE
Description
delete collection of User
Table 5.1. Query parameters
ParameterTypeDescription

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 5.2. HTTP responses
HTTP codeReponse body

200 - OK

Status_v11 schema

401 - Unauthorized

Empty

HTTP method
GET
Description
list or watch objects of kind User
Table 5.3. HTTP responses
HTTP codeReponse body

200 - OK

UserList schema

401 - Unauthorized

Empty

HTTP method
POST
Description
create an User
Table 5.4. Query parameters
ParameterTypeDescription

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.5. Body parameters
ParameterTypeDescription

body

User schema

 
Table 5.6. HTTP responses
HTTP codeReponse body

200 - OK

User schema

201 - Created

User schema

202 - Accepted

User schema

401 - Unauthorized

Empty

5.2.2. /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 5.7. HTTP responses
HTTP codeReponse body

200 - OK

WatchEvent schema

401 - Unauthorized

Empty

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

Table 5.8. Global path parameters
ParameterTypeDescription

name

string

name of the User

HTTP method
DELETE
Description
delete an User
Table 5.9. Query parameters
ParameterTypeDescription

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 5.10. HTTP responses
HTTP codeReponse body

200 - OK

Status_v11 schema

202 - Accepted

Status_v11 schema

401 - Unauthorized

Empty

HTTP method
GET
Description
read the specified User
Table 5.11. HTTP responses
HTTP codeReponse body

200 - OK

User schema

401 - Unauthorized

Empty

HTTP method
PATCH
Description
partially update the specified User
Table 5.12. Query parameters
ParameterTypeDescription

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.13. HTTP responses
HTTP codeReponse body

200 - OK

User schema

201 - Created

User schema

401 - Unauthorized

Empty

HTTP method
PUT
Description
replace the specified User
Table 5.14. Query parameters
ParameterTypeDescription

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.15. Body parameters
ParameterTypeDescription

body

User schema

 
Table 5.16. HTTP responses
HTTP codeReponse body

200 - OK

User schema

201 - Created

User schema

401 - Unauthorized

Empty

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

Table 5.17. Global path parameters
ParameterTypeDescription

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 5.18. HTTP responses
HTTP codeReponse body

200 - OK

WatchEvent schema

401 - Unauthorized

Empty

Red Hat logoGithubRedditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja oBlog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

© 2024 Red Hat, Inc.