ApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 4. OAuthClientAuthorization [oauth.openshift.io/v1]

Description

OAuthClientAuthorization describes an authorization created by an OAuth client

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

Type
object

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

clientName

string

ClientName references the client that created this authorization

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

scopes

array (string)

Scopes is an array of the granted scopes.

userName

string

UserName is the user name that authorized this client

userUID

string

UserUID is the unique UID associated with this authorization. UserUID and UserName must both match for this authorization to be valid.

4.2. API endpoints

The following API endpoints are available:

  • /apis/oauth.openshift.io/v1/oauthclientauthorizations

    • DELETE: delete collection of OAuthClientAuthorization
    • GET: list or watch objects of kind OAuthClientAuthorization
    • POST: create an OAuthClientAuthorization

  • /apis/oauth.openshift.io/v1/watch/oauthclientauthorizations

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

  • /apis/oauth.openshift.io/v1/oauthclientauthorizations/{name}

    • DELETE: delete an OAuthClientAuthorization
    • GET: read the specified OAuthClientAuthorization
    • PATCH: partially update the specified OAuthClientAuthorization
    • PUT: replace the specified OAuthClientAuthorization

  • /apis/oauth.openshift.io/v1/watch/oauthclientauthorizations/{name}

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

4.2.1. /apis/oauth.openshift.io/v1/oauthclientauthorizations

HTTP method
DELETE
Description
delete collection of OAuthClientAuthorization
Table 4.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 4.2. HTTP responses
HTTP codeReponse body

200 - OK

Status_v6 schema

401 - Unauthorized

Empty

HTTP method
GET
Description
list or watch objects of kind OAuthClientAuthorization
Table 4.3. HTTP responses
HTTP codeReponse body

200 - OK

OAuthClientAuthorizationList schema

401 - Unauthorized

Empty

HTTP method
POST
Description
create an OAuthClientAuthorization
Table 4.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 4.5. Body parameters
ParameterTypeDescription

body

OAuthClientAuthorization schema

 
Table 4.6. HTTP responses
HTTP codeReponse body

200 - OK

OAuthClientAuthorization schema

201 - Created

OAuthClientAuthorization schema

202 - Accepted

OAuthClientAuthorization schema

401 - Unauthorized

Empty

4.2.2. /apis/oauth.openshift.io/v1/watch/oauthclientauthorizations

HTTP method
GET
Description
watch individual changes to a list of OAuthClientAuthorization. deprecated: use the 'watch' parameter with a list operation instead.
Table 4.7. HTTP responses
HTTP codeReponse body

200 - OK

WatchEvent schema

401 - Unauthorized

Empty

4.2.3. /apis/oauth.openshift.io/v1/oauthclientauthorizations/{name}

Table 4.8. Global path parameters
ParameterTypeDescription

name

string

name of the OAuthClientAuthorization

HTTP method
DELETE
Description
delete an OAuthClientAuthorization
Table 4.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 4.10. HTTP responses
HTTP codeReponse body

200 - OK

Status_v6 schema

202 - Accepted

Status_v6 schema

401 - Unauthorized

Empty

HTTP method
GET
Description
read the specified OAuthClientAuthorization
Table 4.11. HTTP responses
HTTP codeReponse body

200 - OK

OAuthClientAuthorization schema

401 - Unauthorized

Empty

HTTP method
PATCH
Description
partially update the specified OAuthClientAuthorization
Table 4.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 4.13. HTTP responses
HTTP codeReponse body

200 - OK

OAuthClientAuthorization schema

201 - Created

OAuthClientAuthorization schema

401 - Unauthorized

Empty

HTTP method
PUT
Description
replace the specified OAuthClientAuthorization
Table 4.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 4.15. Body parameters
ParameterTypeDescription

body

OAuthClientAuthorization schema

 
Table 4.16. HTTP responses
HTTP codeReponse body

200 - OK

OAuthClientAuthorization schema

201 - Created

OAuthClientAuthorization schema

401 - Unauthorized

Empty

4.2.4. /apis/oauth.openshift.io/v1/watch/oauthclientauthorizations/{name}

Table 4.17. Global path parameters
ParameterTypeDescription

name

string

name of the OAuthClientAuthorization

HTTP method
GET
Description
watch changes to an object of kind OAuthClientAuthorization. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
Table 4.18. HTTP responses
HTTP codeReponse body

200 - OK

WatchEvent schema

401 - Unauthorized

Empty

Red Hat logoGithubRedditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

© 2024 Red Hat, Inc.