{
  "description": "JWTOIDCAuthEngineConfig is the Schema for the jwtoidcauthengineconfigs API",
  "properties": {
    "apiVersion": {
      "description": "APIVersion defines the versioned schema of this representation of an object.\nServers should convert recognized schemas to the latest internal value, and\nmay reject unrecognized values.\nMore info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources",
      "type": [
        "string",
        "null"
      ]
    },
    "kind": {
      "description": "Kind is a string value representing the REST resource this object represents.\nServers may infer this from the endpoint the client submits requests to.\nCannot be updated.\nIn CamelCase.\nMore info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds",
      "type": [
        "string",
        "null"
      ]
    },
    "metadata": {
      "type": [
        "object",
        "null"
      ]
    },
    "spec": {
      "additionalProperties": false,
      "description": "JWTOIDCAuthEngineConfigSpec defines the desired state of JWTOIDCAuthEngineConfig",
      "properties": {
        "JWKSCAPEM": {
          "default": "",
          "description": "The CA certificate or chain of certificates, in PEM format, to use to validate connections to the JWKS URL.\nIf not set, system certificates are used.",
          "type": [
            "string",
            "null"
          ]
        },
        "JWKSURL": {
          "default": "",
          "description": "JWKS URL to use to authenticate signatures.\nCannot be used with \"oidc_discovery_url\" or \"jwt_validation_pubkeys\"",
          "type": [
            "string",
            "null"
          ]
        },
        "JWTSupportedAlgs": {
          "description": "A list of supported signing algorithms. Defaults to [RS256] for OIDC roles. Defaults to all available algorithms for JWT roles\nkubebuilder:validation:UniqueItems=true",
          "items": {
            "type": "string"
          },
          "type": [
            "array",
            "null"
          ],
          "x-kubernetes-list-type": "set"
        },
        "JWTValidationPubKeys": {
          "description": "A list of PEM-encoded public keys to use to authenticate signatures locally. Cannot be used with \"jwks_url\" or \"oidc_discovery_url\"\nkubebuilder:validation:UniqueItems=true",
          "items": {
            "type": "string"
          },
          "type": [
            "array",
            "null"
          ],
          "x-kubernetes-list-type": "set"
        },
        "OIDCClientID": {
          "default": "",
          "description": "The OAuth Client ID from the provider for OIDC roles.",
          "type": [
            "string",
            "null"
          ]
        },
        "OIDCCredentials": {
          "additionalProperties": false,
          "description": "OIDCCredentials from the provider for OIDC roles\nOIDCCredentials consists in OIDCClientID and OIDCClientSecret, which can be created as Kubernetes Secret, VaultSecret or RandomSecret",
          "properties": {
            "passwordKey": {
              "default": "password",
              "description": "PasswordKey key to be used when retrieving the password, required with VaultSecrets and Kubernetes secrets, ignored with RandomSecret",
              "type": [
                "string",
                "null"
              ]
            },
            "randomSecret": {
              "additionalProperties": false,
              "description": "RandomSecret retrieves the credentials from the Vault secret corresponding to this RandomSecret. This will map the \"username\" and \"password\" keys of the secret to the username and password of this config. All other keys will be ignored. If the RandomSecret is refreshed the operator retrieves the new secret from Vault and updates this configuration. Only one of RootCredentialsFromVaultSecret or RootCredentialsFromSecret or RootCredentialsFromRandomSecret can be specified.\nWhen using randomSecret a username must be specified in the spec.username\npassword: Specifies the password to use when connecting with the username. This value will not be returned by Vault when performing a read upon the configuration. This is typically used in the connection_url field via the templating directive \"{{\"password\"}}\"\".",
              "properties": {
                "name": {
                  "description": "Name of the referent.\nMore info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\nTODO: Add other useful fields. apiVersion, kind, uid?",
                  "type": [
                    "string",
                    "null"
                  ]
                }
              },
              "type": [
                "object",
                "null"
              ],
              "x-kubernetes-map-type": "atomic"
            },
            "secret": {
              "additionalProperties": false,
              "description": "Secret retrieves the credentials from a Kubernetes secret. The secret must be of basicauth type (https://kubernetes.io/docs/concepts/configuration/secret/#basic-authentication-secret). This will map the \"username\" and \"password\" keys of the secret to the username and password of this config. If the kubernetes secret is updated, this configuration will also be updated. All other keys will be ignored. Only one of RootCredentialsFromVaultSecret or RootCredentialsFromSecret or RootCredentialsFromRandomSecret can be specified.\nusername: Specifies the name of the user to use as the \"root\" user when connecting to the database. This \"root\" user is used to create/update/delete users managed by these plugins, so you will need to ensure that this user has permissions to manipulate users appropriate to the database. This is typically used in the connection_url field via the templating directive \"{{\"username\"}}\" or \"{{\"name\"}}\".\npassword: Specifies the password to use when connecting with the username. This value will not be returned by Vault when performing a read upon the configuration. This is typically used in the connection_url field via the templating directive \"{{\"password\"}}\".\nIf username is provided as spec.username, it takes precedence over the username retrieved from the referenced secret",
              "properties": {
                "name": {
                  "description": "Name of the referent.\nMore info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\nTODO: Add other useful fields. apiVersion, kind, uid?",
                  "type": [
                    "string",
                    "null"
                  ]
                }
              },
              "type": [
                "object",
                "null"
              ],
              "x-kubernetes-map-type": "atomic"
            },
            "usernameKey": {
              "default": "username",
              "description": "UsernameKey key to be used when retrieving the username, optional with VaultSecrets and Kubernetes secrets, ignored with RandomSecret",
              "type": [
                "string",
                "null"
              ]
            },
            "vaultSecret": {
              "additionalProperties": false,
              "description": "VaultSecret retrieves the credentials from a Vault secret. This will map the \"username\" and \"password\" keys of the secret to the username and password of this config. All other keys will be ignored. Only one of RootCredentialsFromVaultSecret or RootCredentialsFromSecret or RootCredentialsFromRandomSecret can be specified.\nusername: Specifies the name of the user to use as the \"root\" user when connecting to the database. This \"root\" user is used to create/update/delete users managed by these plugins, so you will need to ensure that this user has permissions to manipulate users appropriate to the database. This is typically used in the connection_url field via the templating directive \"{{\"username\"}}\" or \"{{\"name\"}}\".\npassword: Specifies the password to use when connecting with the username. This value will not be returned by Vault when performing a read upon the configuration. This is typically used in the connection_url field via the templating directive \"{{\"password\"}}\".\nIf username is provided as spec.username, it takes precedence over the username retrieved from the referenced secret",
              "properties": {
                "path": {
                  "description": "Path is the path to the secret",
                  "type": [
                    "string",
                    "null"
                  ]
                }
              },
              "type": [
                "object",
                "null"
              ]
            }
          },
          "type": [
            "object",
            "null"
          ]
        },
        "OIDCDiscoveryCAPEM": {
          "default": "",
          "description": "The CA certificate or chain of certificates, in PEM format, to use to validate connections to the OIDC Discovery URL.\nIf not set, system certificates are used",
          "type": [
            "string",
            "null"
          ]
        },
        "OIDCDiscoveryURL": {
          "default": "",
          "description": "The OIDC Discovery URL, without any .well-known component (base path). Cannot be used with \"jwks_url\" or \"jwt_validation_pubkeys\"",
          "type": [
            "string",
            "null"
          ]
        },
        "OIDCResponseMode": {
          "default": "",
          "description": "The response mode to be used in the OAuth2 request.\nAllowed values are \"query\" and \"form_post\". Defaults to \"query\".\nIf using Vault namespaces, and oidc_response_mode is \"form_post\", then \"namespace_in_state\" should be set to false",
          "type": [
            "string",
            "null"
          ]
        },
        "OIDCResponseTypes": {
          "description": "The response types to request. Allowed values are \"code\" and \"id_token\". Defaults to \"code\".\nNote: \"id_token\" may only be used if \"oidc_response_mode\" is set to \"form_post\"\nkubebuilder:validation:UniqueItems=true",
          "items": {
            "type": "string"
          },
          "type": [
            "array",
            "null"
          ],
          "x-kubernetes-list-type": "set"
        },
        "authentication": {
          "additionalProperties": false,
          "properties": {
            "namespace": {
              "description": "Namespace is the Vault namespace to be used in all the operations withing this connection/authentication. Only available in Vault Enterprise.",
              "type": [
                "string",
                "null"
              ]
            },
            "path": {
              "default": "kubernetes",
              "description": "Path is the path of the role used for this kube auth authentication. The operator will try to authenticate at {[namespace/]}auth/{spec.path}",
              "pattern": "^(?:/?[\\w;:@\u0026=\\$-\\.\\+]*)+/?",
              "type": [
                "string",
                "null"
              ]
            },
            "role": {
              "description": "Role the role to be used during authentication",
              "type": [
                "string",
                "null"
              ]
            },
            "serviceAccount": {
              "additionalProperties": false,
              "default": {
                "name": "default"
              },
              "description": "ServiceAccount is the service account used for the kube auth authentication",
              "properties": {
                "name": {
                  "description": "Name of the referent.\nMore info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\nTODO: Add other useful fields. apiVersion, kind, uid?",
                  "type": [
                    "string",
                    "null"
                  ]
                }
              },
              "type": [
                "object",
                "null"
              ],
              "x-kubernetes-map-type": "atomic"
            }
          },
          "type": [
            "object",
            "null"
          ]
        },
        "boundIssuer": {
          "default": "",
          "description": "The value against which to match the iss claim in a JWT",
          "type": [
            "string",
            "null"
          ]
        },
        "connection": {
          "additionalProperties": false,
          "description": "Connection represents the information needed to connect to Vault. This operator uses the standard Vault environment variables to connect to Vault. If you need to override those settings and for example connect to a different Vault instance, you can do with this section of the CR.",
          "properties": {
            "address": {
              "description": "Address Address of the Vault server expressed as a URL and port, for example: https://127.0.0.1:8200/",
              "type": [
                "string",
                "null"
              ]
            },
            "maxRetries": {
              "description": "MaxRetries Maximum number of retries when certain error codes are encountered. The default is 2, for three total attempts. Set this to 0 or less to disable retrying. Error codes that are retried are 412 (client consistency requirement not satisfied) and all 5xx except for 501 (not implemented).",
              "type": [
                "integer",
                "null"
              ]
            },
            "tLSConfig": {
              "additionalProperties": false,
              "properties": {
                "cacert": {
                  "description": "Cacert Path to a PEM-encoded CA certificate file on the local disk. This file is used to verify the Vault server's SSL certificate. This environment variable takes precedence over a cert passed via the secret.",
                  "type": [
                    "string",
                    "null"
                  ]
                },
                "skipVerify": {
                  "description": "SkipVerify Do not verify Vault's presented certificate before communicating with it. Setting this variable is not recommended and voids Vault's security model.",
                  "type": [
                    "boolean",
                    "null"
                  ]
                },
                "tlsSecret": {
                  "additionalProperties": false,
                  "description": "TLSSecret namespace-local secret containing the tls material for the connection. the expected keys for the secret are: ca bundle -\u003e \"ca.crt\", certificate -\u003e \"tls.crt\", key -\u003e \"tls.key\"",
                  "properties": {
                    "name": {
                      "description": "Name of the referent.\nMore info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names\nTODO: Add other useful fields. apiVersion, kind, uid?",
                      "type": [
                        "string",
                        "null"
                      ]
                    }
                  },
                  "type": [
                    "object",
                    "null"
                  ],
                  "x-kubernetes-map-type": "atomic"
                },
                "tlsServerName": {
                  "description": "TLSServerName Name to use as the SNI host when connecting via TLS.",
                  "type": [
                    "string",
                    "null"
                  ]
                }
              },
              "type": [
                "object",
                "null"
              ]
            },
            "timeOut": {
              "description": "Timeout Timeout variable. The default value is 60s.",
              "type": [
                "string",
                "null"
              ]
            }
          },
          "type": [
            "object",
            "null"
          ]
        },
        "defaultRole": {
          "default": "",
          "description": "The default role to use if none is provided during login",
          "type": [
            "string",
            "null"
          ]
        },
        "namespaceInState": {
          "default": true,
          "description": "Pass namespace in the OIDC state parameter instead of as a separate query parameter.\nWith this setting, the allowed redirect URL(s) in Vault and on the provider side should not contain a namespace query parameter.\nThis means only one redirect URL entry needs to be maintained on the provider side for all vault namespaces that will be authenticating against it.\nDefaults to true for new configs",
          "type": [
            "boolean",
            "null"
          ]
        },
        "path": {
          "description": "Path at which to make the configuration.\nThe final path in Vault will be {[spec.authentication.namespace]}/auth/{spec.path}/config/{metadata.name}.\nThe authentication role must have the following capabilities = [ \"create\", \"read\", \"update\", \"delete\"] on that path.",
          "pattern": "^(?:/?[\\w;:@\u0026=\\$-\\.\\+]*)+/?",
          "type": [
            "string",
            "null"
          ]
        },
        "providerConfig": {
          "default": {},
          "description": "Configuration options for provider-specific handling. Providers with specific handling include: Azure, Google.\nThe options are described in each provider's section in OIDC Provider Setup",
          "x-kubernetes-preserve-unknown-fields": true
        }
      },
      "type": [
        "object",
        "null"
      ]
    },
    "status": {
      "additionalProperties": false,
      "description": "JWTOIDCAuthEngineConfigStatus defines the observed state of JWTOIDCAuthEngineConfig",
      "properties": {
        "conditions": {
          "items": {
            "additionalProperties": false,
            "description": "Condition contains details for one aspect of the current state of this API Resource.\n---\nThis struct is intended for direct use as an array at the field path .status.conditions.  For example,\n\n\n\ttype FooStatus struct{\n\t    // Represents the observations of a foo's current state.\n\t    // Known .status.conditions.type are: \"Available\", \"Progressing\", and \"Degraded\"\n\t    // +patchMergeKey=type\n\t    // +patchStrategy=merge\n\t    // +listType=map\n\t    // +listMapKey=type\n\t    Conditions []metav1.Condition `json:\"conditions,omitempty\" patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t    // other fields\n\t}",
            "properties": {
              "lastTransitionTime": {
                "description": "lastTransitionTime is the last time the condition transitioned from one status to another.\nThis should be when the underlying condition changed.  If that is not known, then using the time when the API field changed is acceptable.",
                "format": "date-time",
                "type": "string"
              },
              "message": {
                "description": "message is a human readable message indicating details about the transition.\nThis may be an empty string.",
                "maxLength": 32768,
                "type": "string"
              },
              "observedGeneration": {
                "description": "observedGeneration represents the .metadata.generation that the condition was set based upon.\nFor instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date\nwith respect to the current state of the instance.",
                "format": "int64",
                "minimum": 0,
                "type": [
                  "integer",
                  "null"
                ]
              },
              "reason": {
                "description": "reason contains a programmatic identifier indicating the reason for the condition's last transition.\nProducers of specific condition types may define expected values and meanings for this field,\nand whether the values are considered a guaranteed API.\nThe value should be a CamelCase string.\nThis field may not be empty.",
                "maxLength": 1024,
                "minLength": 1,
                "pattern": "^[A-Za-z]([A-Za-z0-9_,:]*[A-Za-z0-9_])?$",
                "type": "string"
              },
              "status": {
                "description": "status of the condition, one of True, False, Unknown.",
                "enum": [
                  "True",
                  "False",
                  "Unknown"
                ],
                "type": "string"
              },
              "type": {
                "description": "type of condition in CamelCase or in foo.example.com/CamelCase.\n---\nMany .condition.type values are consistent across resources like Available, but because arbitrary conditions can be\nuseful (see .node.status.conditions), the ability to deconflict is important.\nThe regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)",
                "maxLength": 316,
                "pattern": "^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$",
                "type": "string"
              }
            },
            "required": [
              "lastTransitionTime",
              "message",
              "reason",
              "status",
              "type"
            ],
            "type": "object"
          },
          "type": [
            "array",
            "null"
          ],
          "x-kubernetes-list-map-keys": [
            "type"
          ],
          "x-kubernetes-list-type": "map"
        }
      },
      "type": [
        "object",
        "null"
      ]
    }
  },
  "type": "object"
}