Package v1alpha1 is the v1alpha1 version of the Pinniped concierge authentication API.
Condition status of a resource (mirrored from the metav1.Condition type added in Kubernetes 1.19). In a future API version we can switch to using the upstream type. See https://github.com/kubernetes/apimachinery/blob/v0.19.0/pkg/apis/meta/v1/types.go#L1353-L1413.
| Field | Description |
|---|---|
|
type of condition in CamelCase or in foo.example.com/CamelCase. --- Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be useful (see .node.status.conditions), the ability to deconflict is important. The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt) |
|
status of the condition, one of True, False, Unknown. |
|
observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance. |
|
lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable. |
|
reason contains a programmatic identifier indicating the reason for the condition’s last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty. |
|
message is a human readable message indicating details about the transition. This may be an empty string. |
ConditionStatus is effectively an enum type for Condition.Status.
JWTAuthenticator describes the configuration of a JWT authenticator. Upon receiving a signed JWT, a JWTAuthenticator will performs some validation on it (e.g., valid signature, existence of claims, etc.) and extract the username and groups from the token.
| Field | Description |
|---|---|
|
Refer to Kubernetes API documentation for fields of |
|
Spec for configuring the authenticator. |
|
Status of the authenticator. |
Spec for configuring a JWT authenticator.
| Field | Description |
|---|---|
|
Issuer is the OIDC issuer URL that will be used to discover public signing keys. Issuer is also used to validate the "iss" JWT claim. |
|
Audience is the required value of the "aud" JWT claim. |
|
Claims allows customization of the claims that will be mapped to user identity for Kubernetes access. |
|
TLS configuration for communicating with the OIDC provider. |
Status of a JWT authenticator.
| Field | Description |
|---|---|
|
Represents the observations of the authenticator’s current state. |
JWTTokenClaims allows customization of the claims that will be mapped to user identity for Kubernetes access.
| Field | Description |
|---|---|
|
Groups is the name of the claim which should be read to extract the user’s group membership from the JWT token. When not specified, it will default to "groups". |
|
Username is the name of the claim which should be read to extract the username from the JWT token. When not specified, it will default to "username". |
Configuration for configuring TLS on various authenticators.
| Field | Description |
|---|---|
|
X.509 Certificate Authority (base64-encoded PEM bundle). If omitted, a default set of system roots will be trusted. |
WebhookAuthenticator describes the configuration of a webhook authenticator.
| Field | Description |
|---|---|
|
Refer to Kubernetes API documentation for fields of |
Spec for configuring the authenticator. |
|
|
Status of the authenticator. |
Spec for configuring a webhook authenticator.
| Field | Description |
|---|---|
|
Webhook server endpoint URL. |
|
TLS configuration. |
Status of a webhook authenticator.
| Field | Description |
|---|---|
|
Represents the observations of the authenticator’s current state. |
Package clientsecret is the internal version of the Pinniped client secret API.
OIDCClientSecretRequest can be used to update the client secrets associated with an OIDCClient.
| Field | Description |
|---|---|
|
Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#names |
|
GenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided. If this field is used, the name returned to the client will be different than the name passed. This value will also be combined with a unique suffix. The provided value has the same validation rules as the Name field, and may be truncated by the length of the suffix required to make the value unique on the server. If this field is specified and the generated name exists, the server will return a 409. Applied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#idempotency |
|
Namespace defines the space within which each name must be unique. An empty namespace is equivalent to the "default" namespace, but "default" is the canonical representation. Not all objects are required to be scoped to a namespace - the value of this field for those objects will be empty. Must be a DNS_LABEL. Cannot be updated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces |
|
Deprecated: selfLink is a legacy read-only field that is no longer populated by the system. |
|
UID is the unique in time and space value for this object. It is typically generated by the server on successful creation of a resource and is not allowed to change on PUT operations. Populated by the system. Read-only. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids |
|
An opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed. May be used for optimistic concurrency, change detection, and the watch operation on a resource or set of resources. Clients must treat these values as opaque and passed unmodified back to the server. They may only be valid for a particular resource or set of resources. Populated by the system. Read-only. Value must be treated as opaque by clients and . More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency |
|
A sequence number representing a specific generation of the desired state. Populated by the system. Read-only. |
|
CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC. Populated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata |
|
DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource is expected to be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field, once the finalizers list is empty. As long as the finalizers list contains items, deletion is blocked. Once the deletionTimestamp is set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time. For example, a user may request that a pod is deleted in 30 seconds. The Kubelet will react by sending a graceful termination signal to the containers in the pod. After that 30 seconds, the Kubelet will send a hard termination signal (SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after this timestamp, until an administrator or automated process can determine the resource is fully terminated. If not set, graceful deletion of the object has not been requested. Populated by the system when a graceful deletion is requested. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata |
|
Number of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set. May only be shortened. Read-only. |
|
Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels |
|
Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations |
|
List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller. |
|
Must be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed. Finalizers may be processed and removed in any order. Order is NOT enforced because it introduces significant risk of stuck finalizers. finalizers is a shared field, any actor with permission can reorder it. If the finalizer list is processed in order, then this can lead to a situation in which the component responsible for the first finalizer in the list is waiting for a signal (field value, external system, or other) produced by a component responsible for a finalizer later in the list, resulting in a deadlock. Without enforced ordering finalizers are free to order amongst themselves and are not vulnerable to ordering changes in the list. |
|
ManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn’t need to set or understand this field. A workflow can be the user’s name, a controller’s name, or the name of a specific apply path like "ci-cd". The set of fields is always in the version that the workflow used when modifying the object. |
Spec of the OIDCClientSecretRequest.
| Field | Description |
|---|---|
|
Request a new client secret to for the OIDCClient referenced by the metadata.name field. |
|
Revoke the old client secrets associated with the OIDCClient referenced by the metadata.name field. |
Status of the OIDCClientSecretRequest.
| Field | Description |
|---|---|
|
The unencrypted OIDC Client Secret. This will only be shared upon creation and cannot be recovered if lost. |
|
The total number of client secrets associated with the OIDCClient referenced by the metadata.name field. |
Package v1alpha1 is the v1alpha1 version of the Pinniped client secret API.
OIDCClientSecretRequest can be used to update the client secrets associated with an OIDCClient.
| Field | Description |
|---|---|
|
Refer to Kubernetes API documentation for fields of |
Spec of the OIDCClientSecretRequest.
| Field | Description |
|---|---|
|
Request a new client secret to for the OIDCClient referenced by the metadata.name field. |
|
Revoke the old client secrets associated with the OIDCClient referenced by the metadata.name field. |
Status of the OIDCClientSecretRequest.
| Field | Description |
|---|---|
|
The unencrypted OIDC Client Secret. This will only be shared upon creation and cannot be recovered if lost. |
|
The total number of client secrets associated with the OIDCClient referenced by the metadata.name field. |
Package v1alpha1 is the v1alpha1 version of the Pinniped concierge configuration API.
CredentialIssuer describes the configuration and status of the Pinniped Concierge credential issuer.
| Field | Description |
|---|---|
|
Refer to Kubernetes API documentation for fields of |
|
Spec describes the intended configuration of the Concierge. |
|
CredentialIssuerStatus describes the status of the Concierge. |
CredentialIssuerFrontend describes how to connect using a particular integration strategy.
| Field | Description |
|---|---|
|
Type describes which frontend mechanism clients can use with a strategy. |
|
TokenCredentialRequestAPIInfo describes the parameters for the TokenCredentialRequest API on this Concierge. This field is only set when Type is "TokenCredentialRequestAPI". |
|
ImpersonationProxyInfo describes the parameters for the impersonation proxy on this Concierge. This field is only set when Type is "ImpersonationProxy". |
CredentialIssuerKubeConfigInfo provides the information needed to form a valid Pinniped-based kubeconfig using this credential issuer. This type is deprecated and will be removed in a future version.
| Field | Description |
|---|---|
|
The K8s API server URL. |
|
The K8s API server CA bundle. |
CredentialIssuerSpec describes the intended configuration of the Concierge.
| Field | Description |
|---|---|
|
ImpersonationProxy describes the intended configuration of the Concierge impersonation proxy. |
CredentialIssuerStatus describes the status of the Concierge.
| Field | Description |
|---|---|
|
List of integration strategies that were attempted by Pinniped. |
|
Information needed to form a valid Pinniped-based kubeconfig using this credential issuer. This field is deprecated and will be removed in a future version. |
CredentialIssuerStrategy describes the status of an integration strategy that was attempted by Pinniped.
| Field | Description |
|---|---|
|
Type of integration attempted. |
|
Status of the attempted integration strategy. |
|
Reason for the current status. |
|
Human-readable description of the current status. |
|
When the status was last checked. |
|
Frontend describes how clients can connect using this strategy. |
ImpersonationProxyInfo describes the parameters for the impersonation proxy on this Concierge.
| Field | Description |
|---|---|
|
Endpoint is the HTTPS endpoint of the impersonation proxy. |
|
CertificateAuthorityData is the base64-encoded PEM CA bundle of the impersonation proxy. |
ImpersonationProxyMode enumerates the configuration modes for the impersonation proxy.
ImpersonationProxyServiceSpec describes how the Concierge should provision a Service to expose the impersonation proxy.
| Field | Description |
|---|---|
Type specifies the type of Service to provision for the impersonation proxy. If the type is "None", then the "spec.impersonationProxy.externalEndpoint" field must be set to a non-empty value so that the Concierge can properly advertise the endpoint in the CredentialIssuer’s status. |
|
|
LoadBalancerIP specifies the IP address to set in the spec.loadBalancerIP field of the provisioned Service. This is not supported on all cloud providers. |
|
Annotations specifies zero or more key/value pairs to set as annotations on the provisioned Service. |
ImpersonationProxyServiceType enumerates the types of service that can be provisioned for the impersonation proxy.
ImpersonationProxySpec describes the intended configuration of the Concierge impersonation proxy.
| Field | Description |
|---|---|
Mode configures whether the impersonation proxy should be started: - "disabled" explicitly disables the impersonation proxy. This is the default. - "enabled" explicitly enables the impersonation proxy. - "auto" enables or disables the impersonation proxy based upon the cluster in which it is running. |
|
|
Service describes the configuration of the Service provisioned to expose the impersonation proxy to clients. |
|
ExternalEndpoint describes the HTTPS endpoint where the proxy will be exposed. If not set, the proxy will be served using the external name of the LoadBalancer service or the cluster service DNS name. This field must be non-empty when spec.impersonationProxy.service.type is "None". |
TokenCredentialRequestAPIInfo describes the parameters for the TokenCredentialRequest API on this Concierge.
| Field | Description |
|---|---|
|
Server is the Kubernetes API server URL. |
|
CertificateAuthorityData is the base64-encoded Kubernetes API server CA bundle. |
Package v1alpha1 is the v1alpha1 version of the Pinniped supervisor configuration API.
Condition status of a resource (mirrored from the metav1.Condition type added in Kubernetes 1.19). In a future API version we can switch to using the upstream type. See https://github.com/kubernetes/apimachinery/blob/v0.19.0/pkg/apis/meta/v1/types.go#L1353-L1413.
| Field | Description |
|---|---|
|
type of condition in CamelCase or in foo.example.com/CamelCase. --- Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be useful (see .node.status.conditions), the ability to deconflict is important. The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt) |
|
status of the condition, one of True, False, Unknown. |
|
observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance. |
|
lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable. |
|
reason contains a programmatic identifier indicating the reason for the condition’s last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty. |
|
message is a human readable message indicating details about the transition. This may be an empty string. |
FederationDomain describes the configuration of an OIDC provider.
| Field | Description |
|---|---|
|
Refer to Kubernetes API documentation for fields of |
|
Spec of the OIDC provider. |
|
Status of the OIDC provider. |
FederationDomainSecrets holds information about this OIDC Provider’s secrets.
| Field | Description |
|---|---|
|
JWKS holds the name of the corev1.Secret in which this OIDC Provider’s signing/verification keys are stored. If it is empty, then the signing/verification keys are either unknown or they don’t exist. |
|
TokenSigningKey holds the name of the corev1.Secret in which this OIDC Provider’s key for signing tokens is stored. |
|
StateSigningKey holds the name of the corev1.Secret in which this OIDC Provider’s key for signing state parameters is stored. |
|
StateSigningKey holds the name of the corev1.Secret in which this OIDC Provider’s key for encrypting state parameters is stored. |
FederationDomainSpec is a struct that describes an OIDC Provider.
| Field | Description |
|---|---|
|
Issuer is the OIDC Provider’s issuer, per the OIDC Discovery Metadata document, as well as the identifier that it will use for the iss claim in issued JWTs. This field will also be used as the base URL for any endpoints used by the OIDC Provider (e.g., if your issuer is https://example.com/foo, then your authorization endpoint will look like https://example.com/foo/some/path/to/auth/endpoint). See https://openid.net/specs/openid-connect-discovery-1_0.html#rfc.section.3 for more information. |
TLS configures how this FederationDomain is served over Transport Layer Security (TLS). |
FederationDomainStatus is a struct that describes the actual state of an OIDC Provider.
| Field | Description |
|---|---|
|
Status holds an enum that describes the state of this OIDC Provider. Note that this Status can represent success or failure. |
|
Message provides human-readable details about the Status. |
|
LastUpdateTime holds the time at which the Status was last updated. It is a pointer to get around some undesirable behavior with respect to the empty metav1.Time value (see kubernetes/kubernetes#86811). |
|
Secrets contains information about this OIDC Provider’s secrets. |
FederationDomainTLSSpec is a struct that describes the TLS configuration for an OIDC Provider.
| Field | Description |
|---|---|
|
SecretName is an optional name of a Secret in the same namespace, of type |
OIDCClient describes the configuration of an OIDC client.
| Field | Description |
|---|---|
|
Refer to Kubernetes API documentation for fields of |
|
Spec of the OIDC client. |
|
Status of the OIDC client. |
OIDCClientSpec is a struct that describes an OIDCClient.
| Field | Description |
|---|---|
|
allowedRedirectURIs is a list of the allowed redirect_uri param values that should be accepted during OIDC flows with this client. Any other uris will be rejected. Must be a URI with the https scheme, unless the hostname is 127.0.0.1 or ::1 which may use the http scheme. Port numbers are not required for 127.0.0.1 or ::1 and are ignored when checking for a matching redirect_uri. |
|
allowedGrantTypes is a list of the allowed grant_type param values that should be accepted during OIDC flows with this client. Must only contain the following values: - authorization_code: allows the client to perform the authorization code grant flow, i.e. allows the webapp to authenticate users. This grant must always be listed. - refresh_token: allows the client to perform refresh grants for the user to extend the user’s session. This grant must be listed if allowedScopes lists offline_access. - urn:ietf:params:oauth:grant-type:token-exchange: allows the client to perform RFC8693 token exchange, which is a step in the process to be able to get a cluster credential for the user. This grant must be listed if allowedScopes lists pinniped:request-audience. |
|
allowedScopes is a list of the allowed scopes param values that should be accepted during OIDC flows with this client. Must only contain the following values: - openid: The client is allowed to request ID tokens. ID tokens only include the required claims by default (iss, sub, aud, exp, iat). This scope must always be listed. - offline_access: The client is allowed to request an initial refresh token during the authorization code grant flow. This scope must be listed if allowedGrantTypes lists refresh_token. - pinniped:request-audience: The client is allowed to request a new audience value during a RFC8693 token exchange, which is a step in the process to be able to get a cluster credential for the user. openid, username and groups scopes must be listed when this scope is present. This scope must be listed if allowedGrantTypes lists urn:ietf:params:oauth:grant-type:token-exchange. - username: The client is allowed to request that ID tokens contain the user’s username. Without the username scope being requested and allowed, the ID token will not contain the user’s username. - groups: The client is allowed to request that ID tokens contain the user’s group membership, if their group membership is discoverable by the Supervisor. Without the groups scope being requested and allowed, the ID token will not contain groups. |
OIDCClientStatus is a struct that describes the actual state of an OIDCClient.
| Field | Description |
|---|---|
|
phase summarizes the overall status of the OIDCClient. |
|
conditions represent the observations of an OIDCClient’s current state. |
|
totalClientSecrets is the current number of client secrets that are detected for this OIDCClient. |
Package identity is the internal version of the Pinniped identity API.
KubernetesUserInfo represents the current authenticated user, exactly as Kubernetes understands it. Copied from the Kubernetes token review API.
| Field | Description |
|---|---|
|
User is the UserInfo associated with the current user. |
|
Audiences are audience identifiers chosen by the authenticator. |
UserInfo holds the information about the user needed to implement the user.Info interface.
| Field | Description |
|---|---|
|
The name that uniquely identifies this user among all active users. |
|
A unique value that identifies this user across time. If this user is deleted and another user by the same name is added, they will have different UIDs. |
|
The names of groups this user is a part of. |
|
Any additional information provided by the authenticator. |
WhoAmIRequest submits a request to echo back the current authenticated user.
| Field | Description |
|---|---|
|
Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#names |
|
GenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided. If this field is used, the name returned to the client will be different than the name passed. This value will also be combined with a unique suffix. The provided value has the same validation rules as the Name field, and may be truncated by the length of the suffix required to make the value unique on the server. If this field is specified and the generated name exists, the server will return a 409. Applied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#idempotency |
|
Namespace defines the space within which each name must be unique. An empty namespace is equivalent to the "default" namespace, but "default" is the canonical representation. Not all objects are required to be scoped to a namespace - the value of this field for those objects will be empty. Must be a DNS_LABEL. Cannot be updated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces |
|
Deprecated: selfLink is a legacy read-only field that is no longer populated by the system. |
|
UID is the unique in time and space value for this object. It is typically generated by the server on successful creation of a resource and is not allowed to change on PUT operations. Populated by the system. Read-only. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids |
|
An opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed. May be used for optimistic concurrency, change detection, and the watch operation on a resource or set of resources. Clients must treat these values as opaque and passed unmodified back to the server. They may only be valid for a particular resource or set of resources. Populated by the system. Read-only. Value must be treated as opaque by clients and . More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency |
|
A sequence number representing a specific generation of the desired state. Populated by the system. Read-only. |
|
CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC. Populated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata |
|
DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource is expected to be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field, once the finalizers list is empty. As long as the finalizers list contains items, deletion is blocked. Once the deletionTimestamp is set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time. For example, a user may request that a pod is deleted in 30 seconds. The Kubelet will react by sending a graceful termination signal to the containers in the pod. After that 30 seconds, the Kubelet will send a hard termination signal (SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after this timestamp, until an administrator or automated process can determine the resource is fully terminated. If not set, graceful deletion of the object has not been requested. Populated by the system when a graceful deletion is requested. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata |
|
Number of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set. May only be shortened. Read-only. |
|
Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels |
|
Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations |
|
List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller. |
|
Must be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed. Finalizers may be processed and removed in any order. Order is NOT enforced because it introduces significant risk of stuck finalizers. finalizers is a shared field, any actor with permission can reorder it. If the finalizer list is processed in order, then this can lead to a situation in which the component responsible for the first finalizer in the list is waiting for a signal (field value, external system, or other) produced by a component responsible for a finalizer later in the list, resulting in a deadlock. Without enforced ordering finalizers are free to order amongst themselves and are not vulnerable to ordering changes in the list. |
|
ManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn’t need to set or understand this field. A workflow can be the user’s name, a controller’s name, or the name of a specific apply path like "ci-cd". The set of fields is always in the version that the workflow used when modifying the object. |
|
|
|
Status is set by the server in the response to a WhoAmIRequest.
| Field | Description |
|---|---|
|
The current authenticated user, exactly as Kubernetes understands it. |
Package v1alpha1 is the v1alpha1 version of the Pinniped identity API.
KubernetesUserInfo represents the current authenticated user, exactly as Kubernetes understands it. Copied from the Kubernetes token review API.
| Field | Description |
|---|---|
|
User is the UserInfo associated with the current user. |
|
Audiences are audience identifiers chosen by the authenticator. |
UserInfo holds the information about the user needed to implement the user.Info interface.
| Field | Description |
|---|---|
|
The name that uniquely identifies this user among all active users. |
|
A unique value that identifies this user across time. If this user is deleted and another user by the same name is added, they will have different UIDs. |
|
The names of groups this user is a part of. |
|
Any additional information provided by the authenticator. |
WhoAmIRequest submits a request to echo back the current authenticated user.
| Field | Description |
|---|---|
|
Refer to Kubernetes API documentation for fields of |
|
|
|
Status is set by the server in the response to a WhoAmIRequest.
| Field | Description |
|---|---|
|
The current authenticated user, exactly as Kubernetes understands it. |
Package v1alpha1 is the v1alpha1 version of the Pinniped supervisor identity provider (IDP) API.
ActiveDirectoryIdentityProvider describes the configuration of an upstream Microsoft Active Directory identity provider.
| Field | Description |
|---|---|
|
Refer to Kubernetes API documentation for fields of |
Spec for configuring the identity provider. |
|
Status of the identity provider. |
| Field | Description |
|---|---|
|
SecretName contains the name of a namespace-local Secret object that provides the username and password for an Active Directory bind user. This account will be used to perform LDAP searches. The Secret should be of type "kubernetes.io/basic-auth" which includes "username" and "password" keys. The username value should be the full dn (distinguished name) of your bind account, e.g. "cn=bind-account,ou=users,dc=example,dc=com". The password must be non-empty. |
| Field | Description |
|---|---|
|
Base is the dn (distinguished name) that should be used as the search base when searching for groups. E.g. "ou=groups,dc=example,dc=com". Optional, when not specified it will be based on the result of a query for the defaultNamingContext (see https://docs.microsoft.com/en-us/windows/win32/adschema/rootdse). The default behavior searches your entire domain for groups. It may make sense to specify a subtree as a search base if you wish to exclude some groups for security reasons or to make searches faster. |
|
Filter is the ActiveDirectory search filter which should be applied when searching for groups for a user. The pattern "{}" must occur in the filter at least once and will be dynamically replaced by the value of an attribute of the user entry found as a result of the user search. Which attribute’s value is used to replace the placeholder(s) depends on the value of UserAttributeForFilter. E.g. "member={}" or "&(objectClass=groupOfNames)(member={})". For more information about ActiveDirectory filters, see https://ldap.com/ldap-filters. Note that the dn (distinguished name) is not an attribute of an entry, so "dn={}" cannot be used. Optional. When not specified, the default will act as if the filter were specified as "(&(objectClass=group)(member:1.2.840.113556.1.4.1941:={})". This searches nested groups by default. Note that nested group search can be slow for some Active Directory servers. To disable it, you can set the filter to "(&(objectClass=group)(member={})" |
|
UserAttributeForFilter specifies which attribute’s value from the user entry found as a result of the user search will be used to replace the "{}" placeholder(s) in the group search Filter. For example, specifying "uid" as the UserAttributeForFilter while specifying "&(objectClass=posixGroup)(memberUid={})" as the Filter would search for groups by replacing the "{}" placeholder in the Filter with the value of the user’s "uid" attribute. Optional. When not specified, the default will act as if "dn" were specified. For example, leaving UserAttributeForFilter unspecified while specifying "&(objectClass=groupOfNames)(member={})" as the Filter would search for groups by replacing the "{}" placeholder(s) with the dn (distinguished name) of the user. |
Attributes specifies how the group’s information should be read from each ActiveDirectory entry which was found as the result of the group search. |
|
|
The user’s group membership is refreshed as they interact with the supervisor to obtain new credentials (as their old credentials expire). This allows group membership changes to be quickly reflected into Kubernetes clusters. Since group membership is often used to bind authorization policies, it is important to keep the groups observed in Kubernetes clusters in-sync with the identity provider. In some environments, frequent group membership queries may result in a significant performance impact on the identity provider and/or the supervisor. The best approach to handle performance impacts is to tweak the group query to be more performant, for example by disabling nested group search or by using a more targeted group search base. If the group search query cannot be made performant and you are willing to have group memberships remain static for approximately a day, then set skipGroupRefresh to true. This is an insecure configuration as authorization policies that are bound to group membership will not notice if a user has been removed from a particular group until their next login. This is an experimental feature that may be removed or significantly altered in the future. Consumers of this configuration should carefully read all release notes before upgrading to ensure that the meaning of this field has not changed. |
| Field | Description |
|---|---|
|
GroupName specifies the name of the attribute in the Active Directory entries whose value shall become a group name in the user’s list of groups after a successful authentication. The value of this field is case-sensitive and must match the case of the attribute name returned by the ActiveDirectory server in the user’s entry. E.g. "cn" for common name. Distinguished names can be used by specifying lower-case "dn". Optional. When not specified, this defaults to a custom field that looks like "sAMAccountName@domain", where domain is constructed from the domain components of the group DN. |
Spec for configuring an ActiveDirectory identity provider.
| Field | Description |
|---|---|
|
Host is the hostname of this Active Directory identity provider, i.e., where to connect. For example: ldap.example.com:636. |
|
TLS contains the connection settings for how to establish the connection to the Host. |
Bind contains the configuration for how to provide access credentials during an initial bind to the ActiveDirectory server to be allowed to perform searches and binds to validate a user’s credentials during a user’s authentication attempt. |
|
|
UserSearch contains the configuration for searching for a user by name in Active Directory. |
|
GroupSearch contains the configuration for searching for a user’s group membership in ActiveDirectory. |
Status of an Active Directory identity provider.
| Field | Description |
|---|---|
|
Phase summarizes the overall status of the ActiveDirectoryIdentityProvider. |
|
Represents the observations of an identity provider’s current state. |
| Field | Description |
|---|---|
|
Base is the dn (distinguished name) that should be used as the search base when searching for users. E.g. "ou=users,dc=example,dc=com". Optional, when not specified it will be based on the result of a query for the defaultNamingContext (see https://docs.microsoft.com/en-us/windows/win32/adschema/rootdse). The default behavior searches your entire domain for users. It may make sense to specify a subtree as a search base if you wish to exclude some users or to make searches faster. |
|
Filter is the search filter which should be applied when searching for users. The pattern "{}" must occur in the filter at least once and will be dynamically replaced by the username for which the search is being run. E.g. "mail={}" or "&(objectClass=person)(uid={})". For more information about LDAP filters, see https://ldap.com/ldap-filters. Note that the dn (distinguished name) is not an attribute of an entry, so "dn={}" cannot be used. Optional. When not specified, the default will be '(&(objectClass=person)(!(objectClass=computer))(!(showInAdvancedViewOnly=TRUE))(|(sAMAccountName={}")(mail={})(userPrincipalName={})(sAMAccountType=805306368))' This means that the user is a person, is not a computer, the sAMAccountType is for a normal user account, and is not shown in advanced view only (which would likely mean its a system created service account with advanced permissions). Also, either the sAMAccountName, the userPrincipalName, or the mail attribute matches the input username. |
Attributes specifies how the user’s information should be read from the ActiveDirectory entry which was found as the result of the user search. |
| Field | Description |
|---|---|
|
Username specifies the name of the attribute in Active Directory entry whose value shall become the username of the user after a successful authentication. Optional, when empty this defaults to "userPrincipalName". |
|
UID specifies the name of the attribute in the ActiveDirectory entry which whose value shall be used to uniquely identify the user within this ActiveDirectory provider after a successful authentication. Optional, when empty this defaults to "objectGUID". |
Condition status of a resource (mirrored from the metav1.Condition type added in Kubernetes 1.19). In a future API version we can switch to using the upstream type. See https://github.com/kubernetes/apimachinery/blob/v0.19.0/pkg/apis/meta/v1/types.go#L1353-L1413.
| Field | Description |
|---|---|
|
type of condition in CamelCase or in foo.example.com/CamelCase. --- Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be useful (see .node.status.conditions), the ability to deconflict is important. The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt) |
|
status of the condition, one of True, False, Unknown. |
|
observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance. |
|
lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable. |
|
reason contains a programmatic identifier indicating the reason for the condition’s last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty. |
|
message is a human readable message indicating details about the transition. This may be an empty string. |
ConditionStatus is effectively an enum type for Condition.Status.
LDAPIdentityProvider describes the configuration of an upstream Lightweight Directory Access Protocol (LDAP) identity provider.
| Field | Description |
|---|---|
|
Refer to Kubernetes API documentation for fields of |
Spec for configuring the identity provider. |
|
|
Status of the identity provider. |
| Field | Description |
|---|---|
|
SecretName contains the name of a namespace-local Secret object that provides the username and password for an LDAP bind user. This account will be used to perform LDAP searches. The Secret should be of type "kubernetes.io/basic-auth" which includes "username" and "password" keys. The username value should be the full dn (distinguished name) of your bind account, e.g. "cn=bind-account,ou=users,dc=example,dc=com". The password must be non-empty. |
| Field | Description |
|---|---|
|
Base is the dn (distinguished name) that should be used as the search base when searching for groups. E.g. "ou=groups,dc=example,dc=com". When not specified, no group search will be performed and authenticated users will not belong to any groups from the LDAP provider. Also, when not specified, the values of Filter, UserAttributeForFilter, Attributes, and SkipGroupRefresh are ignored. |
|
Filter is the LDAP search filter which should be applied when searching for groups for a user. The pattern "{}" must occur in the filter at least once and will be dynamically replaced by the value of an attribute of the user entry found as a result of the user search. Which attribute’s value is used to replace the placeholder(s) depends on the value of UserAttributeForFilter. For more information about LDAP filters, see https://ldap.com/ldap-filters. Note that the dn (distinguished name) is not an attribute of an entry, so "dn={}" cannot be used. Optional. When not specified, the default will act as if the Filter were specified as "member={}". |
|
UserAttributeForFilter specifies which attribute’s value from the user entry found as a result of the user search will be used to replace the "{}" placeholder(s) in the group search Filter. For example, specifying "uid" as the UserAttributeForFilter while specifying "&(objectClass=posixGroup)(memberUid={})" as the Filter would search for groups by replacing the "{}" placeholder in the Filter with the value of the user’s "uid" attribute. Optional. When not specified, the default will act as if "dn" were specified. For example, leaving UserAttributeForFilter unspecified while specifying "&(objectClass=groupOfNames)(member={})" as the Filter would search for groups by replacing the "{}" placeholder(s) with the dn (distinguished name) of the user. |
|
Attributes specifies how the group’s information should be read from each LDAP entry which was found as the result of the group search. |
|
The user’s group membership is refreshed as they interact with the supervisor to obtain new credentials (as their old credentials expire). This allows group membership changes to be quickly reflected into Kubernetes clusters. Since group membership is often used to bind authorization policies, it is important to keep the groups observed in Kubernetes clusters in-sync with the identity provider. In some environments, frequent group membership queries may result in a significant performance impact on the identity provider and/or the supervisor. The best approach to handle performance impacts is to tweak the group query to be more performant, for example by disabling nested group search or by using a more targeted group search base. If the group search query cannot be made performant and you are willing to have group memberships remain static for approximately a day, then set skipGroupRefresh to true. This is an insecure configuration as authorization policies that are bound to group membership will not notice if a user has been removed from a particular group until their next login. This is an experimental feature that may be removed or significantly altered in the future. Consumers of this configuration should carefully read all release notes before upgrading to ensure that the meaning of this field has not changed. |
| Field | Description |
|---|---|
|
GroupName specifies the name of the attribute in the LDAP entries whose value shall become a group name in the user’s list of groups after a successful authentication. The value of this field is case-sensitive and must match the case of the attribute name returned by the LDAP server in the user’s entry. E.g. "cn" for common name. Distinguished names can be used by specifying lower-case "dn". Optional. When not specified, the default will act as if the GroupName were specified as "dn" (distinguished name). |
Spec for configuring an LDAP identity provider.
| Field | Description |
|---|---|
|
Host is the hostname of this LDAP identity provider, i.e., where to connect. For example: ldap.example.com:636. |
|
TLS contains the connection settings for how to establish the connection to the Host. |
Bind contains the configuration for how to provide access credentials during an initial bind to the LDAP server to be allowed to perform searches and binds to validate a user’s credentials during a user’s authentication attempt. |
|
|
UserSearch contains the configuration for searching for a user by name in the LDAP provider. |
|
GroupSearch contains the configuration for searching for a user’s group membership in the LDAP provider. |
Status of an LDAP identity provider.
| Field | Description |
|---|---|
|
Phase summarizes the overall status of the LDAPIdentityProvider. |
|
Represents the observations of an identity provider’s current state. |
| Field | Description |
|---|---|
|
Base is the dn (distinguished name) that should be used as the search base when searching for users. E.g. "ou=users,dc=example,dc=com". |
|
Filter is the LDAP search filter which should be applied when searching for users. The pattern "{}" must occur in the filter at least once and will be dynamically replaced by the username for which the search is being run. E.g. "mail={}" or "&(objectClass=person)(uid={})". For more information about LDAP filters, see https://ldap.com/ldap-filters. Note that the dn (distinguished name) is not an attribute of an entry, so "dn={}" cannot be used. Optional. When not specified, the default will act as if the Filter were specified as the value from Attributes.Username appended by "={}". When the Attributes.Username is set to "dn" then the Filter must be explicitly specified, since the default value of "dn={}" would not work. |
|
Attributes specifies how the user’s information should be read from the LDAP entry which was found as the result of the user search. |
| Field | Description |
|---|---|
|
Username specifies the name of the attribute in the LDAP entry whose value shall become the username of the user after a successful authentication. This would typically be the same attribute name used in the user search filter, although it can be different. E.g. "mail" or "uid" or "userPrincipalName". The value of this field is case-sensitive and must match the case of the attribute name returned by the LDAP server in the user’s entry. Distinguished names can be used by specifying lower-case "dn". When this field is set to "dn" then the LDAPIdentityProviderUserSearch’s Filter field cannot be blank, since the default value of "dn={}" would not work. |
|
UID specifies the name of the attribute in the LDAP entry which whose value shall be used to uniquely identify the user within this LDAP provider after a successful authentication. E.g. "uidNumber" or "objectGUID". The value of this field is case-sensitive and must match the case of the attribute name returned by the LDAP server in the user’s entry. Distinguished names can be used by specifying lower-case "dn". |
OIDCAuthorizationConfig provides information about how to form the OAuth2 authorization request parameters.
| Field | Description |
|---|---|
|
additionalScopes are the additional scopes that will be requested from your OIDC provider in the authorization request during an OIDC Authorization Code Flow and in the token request during a Resource Owner Password Credentials Grant. Note that the "openid" scope will always be requested regardless of the value in this setting, since it is always required according to the OIDC spec. By default, when this field is not set, the Supervisor will request the following scopes: "openid", "offline_access", "email", and "profile". See https://openid.net/specs/openid-connect-core-1_0.html#ScopeClaims for a description of the "profile" and "email" scopes. See https://openid.net/specs/openid-connect-core-1_0.html#OfflineAccess for a description of the "offline_access" scope. This default value may change in future versions of Pinniped as the standard evolves, or as common patterns used by providers who implement the standard in the ecosystem evolve. By setting this list to anything other than an empty list, you are overriding the default value, so you may wish to include some of "offline_access", "email", and "profile" in your override list. If you do not want any of these scopes to be requested, you may set this list to contain only "openid". Some OIDC providers may also require a scope to get access to the user’s group membership, in which case you may wish to include it in this list. Sometimes the scope to request the user’s group membership is called "groups", but unfortunately this is not specified in the OIDC standard. Generally speaking, you should include any scopes required to cause the appropriate claims to be the returned by your OIDC provider in the ID token or userinfo endpoint results for those claims which you would like to use in the oidcClaims settings to determine the usernames and group memberships of your Kubernetes users. See your OIDC provider’s documentation for more information about what scopes are available to request claims. Additionally, the Pinniped Supervisor requires that your OIDC provider returns refresh tokens to the Supervisor from these authorization flows. For most OIDC providers, the scope required to receive refresh tokens will be "offline_access". See the documentation of your OIDC provider’s authorization and token endpoints for its requirements for what to include in the request in order to receive a refresh token in the response, if anything. Note that it may be safe to send "offline_access" even to providers which do not require it, since the provider may ignore scopes that it does not understand or require (see https://datatracker.ietf.org/doc/html/rfc6749#section-3.3). In the unusual case that you must avoid sending the "offline_access" scope, then you must override the default value of this setting. This is required if your OIDC provider will reject the request when it includes "offline_access" (e.g. GitLab’s OIDC provider). |
|
additionalAuthorizeParameters are extra query parameters that should be included in the authorize request to your OIDC provider in the authorization request during an OIDC Authorization Code Flow. By default, no extra parameters are sent. The standard parameters that will be sent are "response_type", "scope", "client_id", "state", "nonce", "code_challenge", "code_challenge_method", and "redirect_uri". These parameters cannot be included in this setting. Additionally, the "hd" parameter cannot be included in this setting at this time. The "hd" parameter is used by Google’s OIDC provider to provide a hint as to which "hosted domain" the user should use during login. However, Pinniped does not yet support validating the hosted domain in the resulting ID token, so it is not yet safe to use this feature of Google’s OIDC provider with Pinniped. This setting does not influence the parameters sent to the token endpoint in the Resource Owner Password Credentials Grant. The Pinniped Supervisor requires that your OIDC provider returns refresh tokens to the Supervisor from the authorization flows. Some OIDC providers may require a certain value for the "prompt" parameter in order to properly request refresh tokens. See the documentation of your OIDC provider’s authorization endpoint for its requirements for what to include in the request in order to receive a refresh token in the response, if anything. If your provider requires the prompt parameter to request a refresh token, then include it here. Also note that most providers also require a certain scope to be requested in order to receive refresh tokens. See the additionalScopes setting for more information about using scopes to request refresh tokens. |
|
allowPasswordGrant, when true, will allow the use of OAuth 2.0’s Resource Owner Password Credentials Grant (see https://datatracker.ietf.org/doc/html/rfc6749#section-4.3) to authenticate to the OIDC provider using a username and password without a web browser, in addition to the usual browser-based OIDC Authorization Code Flow. The Resource Owner Password Credentials Grant is not officially part of the OIDC specification, so it may not be supported by your OIDC provider. If your OIDC provider supports returning ID tokens from a Resource Owner Password Credentials Grant token request, then you can choose to set this field to true. This will allow end users to choose to present their username and password to the kubectl CLI (using the Pinniped plugin) to authenticate to the cluster, without using a web browser to log in as is customary in OIDC Authorization Code Flow. This may be convenient for users, especially for identities from your OIDC provider which are not intended to represent a human actor, such as service accounts performing actions in a CI/CD environment. Even if your OIDC provider supports it, you may wish to disable this behavior by setting this field to false when you prefer to only allow users of this OIDCIdentityProvider to log in via the browser-based OIDC Authorization Code Flow. Using the Resource Owner Password Credentials Grant means that the Pinniped CLI and Pinniped Supervisor will directly handle your end users' passwords (similar to LDAPIdentityProvider), and you will not be able to require multi-factor authentication or use the other web-based login features of your OIDC provider during Resource Owner Password Credentials Grant logins. allowPasswordGrant defaults to false. |
OIDCClaims provides a mapping from upstream claims into identities.
| Field | Description |
|---|---|
|
Groups provides the name of the ID token claim or userinfo endpoint response claim that will be used to ascertain the groups to which an identity belongs. By default, the identities will not include any group memberships when this setting is not configured. |
|
Username provides the name of the ID token claim or userinfo endpoint response claim that will be used to ascertain an identity’s username. When not set, the username will be an automatically constructed unique string which will include the issuer URL of your OIDC provider along with the value of the "sub" (subject) claim from the ID token. |
|
AdditionalClaimMappings allows for additional arbitrary upstream claim values to be mapped into the "additionalClaims" claim of the ID tokens generated by the Supervisor. This should be specified as a map of new claim names as the keys, and upstream claim names as the values. These new claim names will be nested under the top-level "additionalClaims" claim in ID tokens generated by the Supervisor when this OIDCIdentityProvider was used for user authentication. These claims will be made available to all clients. This feature is not required to use the Supervisor to provide authentication for Kubernetes clusters, but can be used when using the Supervisor for other authentication purposes. When this map is empty or the upstream claims are not available, the "additionalClaims" claim will be excluded from the ID tokens generated by the Supervisor. |
OIDCClient contains information about an OIDC client (e.g., client ID and client secret).
| Field | Description |
|---|---|
|
SecretName contains the name of a namespace-local Secret object that provides the clientID and clientSecret for an OIDC client. If only the SecretName is specified in an OIDCClient struct, then it is expected that the Secret is of type "secrets.pinniped.dev/oidc-client" with keys "clientID" and "clientSecret". |
OIDCIdentityProvider describes the configuration of an upstream OpenID Connect identity provider.
| Field | Description |
|---|---|
|
Refer to Kubernetes API documentation for fields of |
Spec for configuring the identity provider. |
|
|
Status of the identity provider. |
OIDCIdentityProviderSpec is the spec for configuring an OIDC identity provider.
| Field | Description |
|---|---|
|
Issuer is the issuer URL of this OIDC identity provider, i.e., where to fetch /.well-known/openid-configuration. |
|
TLS configuration for discovery/JWKS requests to the issuer. |
|
AuthorizationConfig holds information about how to form the OAuth2 authorization request parameters to be used with this OIDC identity provider. |
|
Claims provides the names of token claims that will be used when inspecting an identity from this OIDC identity provider. |
|
OIDCClient contains OIDC client information to be used used with this OIDC identity provider. |
OIDCIdentityProviderStatus is the status of an OIDC identity provider.
| Field | Description |
|---|---|
|
Phase summarizes the overall status of the OIDCIdentityProvider. |
|
Represents the observations of an identity provider’s current state. |
Parameter is a key/value pair which represents a parameter in an HTTP request.
| Field | Description |
|---|---|
|
The name of the parameter. Required. |
|
The value of the parameter. |
Configuration for TLS parameters related to identity provider integration.
| Field | Description |
|---|---|
|
X.509 Certificate Authority (base64-encoded PEM bundle). If omitted, a default set of system roots will be trusted. |
Package v1alpha1 is the v1alpha1 version of the Pinniped login API.
ClusterCredential is the cluster-specific credential returned on a successful credential request. It contains either a valid bearer token or a valid TLS certificate and corresponding private key for the cluster.
| Field | Description |
|---|---|
|
ExpirationTimestamp indicates a time when the provided credentials expire. |
|
Token is a bearer token used by the client for request authentication. |
|
PEM-encoded client TLS certificates (including intermediates, if any). |
|
PEM-encoded private key for the above certificate. |
TokenCredentialRequest submits an IDP-specific credential to Pinniped in exchange for a cluster-specific credential.
| Field | Description |
|---|---|
|
Refer to Kubernetes API documentation for fields of |
|
Specification of a TokenCredentialRequest, expected on requests to the Pinniped API.
| Field | Description |
|---|---|
|
Bearer token supplied with the credential request. |
|
Reference to an authenticator which can validate this credential request. |
Status of a TokenCredentialRequest, returned on responses to the Pinniped API.
| Field | Description |
|---|---|
|
A Credential will be returned for a successful credential request. |
|
An error message will be returned for an unsuccessful credential request. |