Skip to content

Identity resources · Kind catalogue · Examples

MFALoginEnforcement

API version: identity.openbaoconfig.io/v1alpha1
Scope: Namespaced
Resource: mfaloginenforcements.identity.openbaoconfig.io
Categories: openbao

MFALoginEnforcement requires login MFA at `identity/mfa/login-enforcement/<name>` for the selected auth mounts, auth method types, entities or groups. Use it with one or more MFAMethod objects to force a second factor on sensitive logins.

Example:

spec:
  connectionRef:
    name: openbao
  mfaMethods:
    - methodRef: {name: totp-main}
  authMounts:
    - mountPath: userpass

Example

examples/identity/mfaloginenforcement.yaml
apiVersion: identity.openbaoconfig.io/v1alpha1
kind: MFALoginEnforcement
metadata:
  name: obco-admins-mfa
  namespace: openbao-config
spec:
  connectionRef:
    kind: OpenBaoConnection
    name: openbao
  creationPolicy: CreateOrAdopt
  driftDetection: Enabled
  driftInterval: 30m
  managementPolicy: Manage
  deletionPolicy: Delete
  name: obco-admins-mfa
  mfaMethods:
    - methodRef:
        name: obco-totp
    - methodName: obco-duo
    - methodID: 6f1e3c2a-0000-4000-8000-000000000003
    - methodSelector:
        matchLabels:
          obco.example.com/mfa: required
  authMounts:
    - mountPath: userpass
    - mountRef:
        name: obco-oidc
    - mountAccessor: auth_userpass_0000fake
    - mountSelector:
        matchLabels:
          obco.example.com/mfa: required
  authMethodTypes:
    - userpass
  entities:
    - entityID: 6f1e3c2a-0000-4000-8000-000000000001
    - entityName: obco-alice
    - entityRef:
        name: obco-bob
    - entitySelector:
        matchLabels:
          obco.example.com/mfa: required
  groups:
    - groupID: 6f1e3c2a-0000-4000-8000-000000000002
    - groupName: obco-admins
    - groupRef:
        name: obco-operators
    - groupSelector:
        matchLabels:
          obco.example.com/mfa: required

On GitHub: mfaloginenforcement.yaml, generated sample with every field.

Fields

Defaults below are CRD schema defaults. A blank cell does not imply zero, false or an empty value; see the field description for omission behaviour. Required fields inside an optional object apply only when that object is set.

FieldTypeRequiredDefaultDescriptionValidation
specobjectyesspec is the desired login MFA enforcement at `identity/mfa/login-enforcement/<name>`: logins through the selected auth mounts or by the selected identities must pass the listed MFA methods. Target lists are written as a whole; targets removed from the spec are removed in OpenBao. Set at least one of authMounts, authMethodTypes, entities and groups.
ConstraintsCEL: has(self.name) == has(oldSelf.name) && (!has(self.name) || self.name == oldSelf.name) (name is immutable)
CEL: has(self.authMounts) || has(self.authMethodTypes) || has(self.entities) || has(self.groups) (set at least one of authMounts, authMethodTypes, entities and groups)
CEL: has(self.__namespace__) == has(oldSelf.__namespace__) && (!has(self.__namespace__) || self.__namespace__ == oldSelf.__namespace__) (namespace is immutable)
CEL: self.connectionRef == oldSelf.connectionRef (connectionRef is immutable)
spec.authMethodTypes[]stringnoauthMethodTypes are auth method types whose logins require MFA (`auth_method_types`). At least one mount of each type must exist. Up to 32. Example: `[userpass, oidc]`.
Constraintsitems: <=32
list type: set
each item: length: >=1, <=64
spec.authMounts[]objectnoauthMounts are the auth mounts whose logins require MFA (`auth_method_accessors`). Up to 64. Example: `[{mountPath: userpass}]`.
Constraintsitems: <=64
list type: atomic
spec.authMounts[]objectnoSelects auth mounts by exactly one of an accessor, a mount path, an AuthMount object or a label selector over AuthMount objects.
ConstraintsCEL: [has(self.mountAccessor), has(self.mountPath), has(self.mountRef), has(self.mountSelector)].filter(x, x).size() == 1 (set exactly one of mountAccessor, mountPath, mountRef and mountSelector)
spec.authMounts[].mountAccessorstringnomountAccessor is the accessor of an auth mount. Example: `auth_userpass_1a2b3c4d`.
Constraintslength: <=128
spec.authMounts[].mountPathstringnomountPath is the path of an auth mount without the `auth/` prefix, resolved to its accessor through the connection. Example: `userpass`.
Constraintslength: <=256
spec.authMounts[].mountRefobjectnomountRef names an AuthMount in the same namespace; it must be Ready. Example: `{name: userpass}`.
spec.authMounts[].mountRef.namestringyesName of the referenced object, in the same namespace as this resource. Example: my-app
Constraintslength: >=1, <=253
spec.authMounts[].mountSelectorobjectnomountSelector selects every AuthMount in the same namespace that carries these labels.
spec.authMounts[].mountSelector.matchLabelsmap[string]stringyesLabels an object must carry, all of them, to be selected. Example: {team: payments}
Constraintsproperties: >=1, <=16
CEL: self.all(k, size(k) <= 317 && size(self[k]) <= 63) (label keys must be at most 317 and values at most 63 characters)
spec.connectionRefobjectyesConnection used to reach and log in to OpenBao. Immutable.
spec.connectionRef.kindstringno"OpenBaoConnection"Kind of the connection: OpenBaoConnection (in the same Kubernetes namespace as this resource) or ClusterOpenBaoConnection (cluster-scoped; its allowedNamespaces must select this namespace). Default: OpenBaoConnection.
Constraintsone of: OpenBaoConnection, ClusterOpenBaoConnection
spec.connectionRef.namestringyesName of the OpenBaoConnection or ClusterOpenBaoConnection. Example: openbao
Constraintslength: >=1, <=253
spec.creationPolicystringno"Create"How an object that already exists in OpenBao, and is not yet owned by this resource, is treated. Create (default): create the object; an existing one is refused with reason Conflict. Adopt: take over an existing object and never create one. CreateOrAdopt: create it, or take over an existing one. Settings that always exist in OpenBao (configuration singletons) need Adopt or CreateOrAdopt.
Constraintsone of: Create, Adopt, CreateOrAdopt
spec.deletionPolicystringno"Orphan"What happens in OpenBao when this resource is deleted. Orphan (default): the OpenBao object stays. Delete: the object is removed (a configuration singleton is reset to its defaults); data and key holders (mounts, namespaces, KV data, audit devices, endpoints, transit, PKI, SSH CA and TOTP keys, MFA methods, entities) are removed only while the resource carries the annotation openbaoconfig.io/allow-destructive-delete: "true". Kinds whose OpenBao object cannot be deleted reject Delete.
Constraintsone of: Delete, Orphan
spec.driftDetectionstringno"Enabled"Whether OpenBao is re-read periodically to detect and repair out-of-band changes. Enabled (default): re-read every driftInterval. Disabled: write only when the spec or a referenced Secret changes.
Constraintsone of: Enabled, Disabled
spec.driftIntervalstringnoHow often OpenBao is re-read for drift, as a duration of at least 30s. Default: the operator's interval for the kind (15m for kinds that grant access such as policies, auth mounts and roles, 1h for the rest), with jitter. Example: 30m
Constraintslength: <=32
CEL: duration(self) >= duration('30s') (driftInterval must be at least 30s)
spec.entities[]objectnoentities are the entities whose logins require MFA (`identity_entity_ids`). Up to 256. Example: `[{entityRef: {name: alice}}]`.
Constraintsitems: <=256
list type: atomic
spec.entities[]objectnoSelects OpenBao entities by exactly one of an ID, an OpenBao name, an Entity object or a label selector over Entity objects.
ConstraintsCEL: [has(self.entityID), has(self.entityName), has(self.entityRef), has(self.entitySelector)].filter(x, x).size() == 1 (set exactly one of entityID, entityName, entityRef and entitySelector)
spec.entities[].entityIDstringnoentityID is the OpenBao ID of an entity. Example: `0b1c6a2e-5d1f-4a7e-9b2e-3c4d5e6f7a8b`.
Constraintslength: <=128
spec.entities[].entityNamestringnoentityName is the OpenBao name of an entity, resolved to its ID through the connection. Example: `alice`.
Constraintslength: <=128
spec.entities[].entityRefobjectnoentityRef names an Entity in the same namespace; it must be Ready. Example: `{name: alice}`.
spec.entities[].entityRef.namestringyesName of the referenced object, in the same namespace as this resource. Example: my-app
Constraintslength: >=1, <=253
spec.entities[].entitySelectorobjectnoentitySelector selects every Entity in the same namespace that carries these labels.
spec.entities[].entitySelector.matchLabelsmap[string]stringyesLabels an object must carry, all of them, to be selected. Example: {team: payments}
Constraintsproperties: >=1, <=16
CEL: self.all(k, size(k) <= 317 && size(self[k]) <= 63) (label keys must be at most 317 and values at most 63 characters)
spec.groups[]objectnogroups are identity groups whose members' logins require MFA (`identity_group_ids`). Up to 256. Example: `[{groupName: admins}]`.
Constraintsitems: <=256
list type: atomic
spec.groups[]objectnoSelects OpenBao identity groups by exactly one of an ID, an OpenBao name, a Group object or a label selector over Group objects.
ConstraintsCEL: [has(self.groupID), has(self.groupName), has(self.groupRef), has(self.groupSelector)].filter(x, x).size() == 1 (set exactly one of groupID, groupName, groupRef and groupSelector)
spec.groups[].groupIDstringnogroupID is the OpenBao ID of a group. Example: `5f1c2d3e-4a5b-6c7d-8e9f-0a1b2c3d4e5f`.
Constraintslength: <=128
spec.groups[].groupNamestringnogroupName is the OpenBao name of a group, resolved to its ID through the connection. Example: `billing-admins`.
Constraintslength: <=128
spec.groups[].groupRefobjectnogroupRef names a Group in the same namespace; it must be Ready. Example: `{name: billing-admins}`.
spec.groups[].groupRef.namestringyesName of the referenced object, in the same namespace as this resource. Example: my-app
Constraintslength: >=1, <=253
spec.groups[].groupSelectorobjectnogroupSelector selects every Group in the same namespace that carries these labels.
spec.groups[].groupSelector.matchLabelsmap[string]stringyesLabels an object must carry, all of them, to be selected. Example: {team: payments}
Constraintsproperties: >=1, <=16
CEL: self.all(k, size(k) <= 317 && size(self[k]) <= 63) (label keys must be at most 317 and values at most 63 characters)
spec.managementPolicystringno"Manage"Whether the operator writes to OpenBao. Manage (default): converge OpenBao to the spec, create and delete as the policies say. Observe: only read the object and report drift in the conditions; never write or delete.
Constraintsone of: Manage, Observe
spec.mfaMethods[]objectyesmfaMethods are the MFA methods a login must pass (`mfa_method_ids`). 1-32 entries. Example: `[{methodRef: {name: totp-main}}]`.
Constraintsitems: >=1, <=32
list type: atomic
spec.mfaMethods[]objectnoSelects login MFA methods by exactly one of a method ID, an OpenBao method name, an MFAMethod object or a label selector over MFAMethod objects.
ConstraintsCEL: [has(self.methodID), has(self.methodName), has(self.methodRef), has(self.methodSelector)].filter(x, x).size() == 1 (set exactly one of methodID, methodName, methodRef and methodSelector)
spec.mfaMethods[].methodIDstringnomethodID is the OpenBao ID of an MFA method. Example: `a1b2c3d4-e5f6-7a8b-9c0d-e1f2a3b4c5d6`.
Constraintslength: <=64
spec.mfaMethods[].methodNamestringnomethodName is the OpenBao name of an MFA method in the same OpenBao namespace, resolved to its ID through the connection. Example: `totp-main`.
Constraintslength: <=128
spec.mfaMethods[].methodRefobjectnomethodRef names an MFAMethod in the same namespace; it must be Ready. Example: `{name: totp-main}`.
spec.mfaMethods[].methodRef.namestringyesName of the referenced object, in the same namespace as this resource. Example: my-app
Constraintslength: >=1, <=253
spec.mfaMethods[].methodSelectorobjectnomethodSelector selects every MFAMethod in the same namespace that carries these labels.
spec.mfaMethods[].methodSelector.matchLabelsmap[string]stringyesLabels an object must carry, all of them, to be selected. Example: {team: payments}
Constraintsproperties: >=1, <=16
CEL: self.all(k, size(k) <= 317 && size(self[k]) <= 63) (label keys must be at most 317 and values at most 63 characters)
spec.namestringnoname is the enforcement name in OpenBao. Defaults to metadata.name. Letters, digits, `_`, `.`, `@` and `-`. Immutable. Example: `require-totp`.
Constraintspattern: ^\w([\w.@-]*\w)?$
length: >=1, <=128
spec.namespacestringnoOpenBao namespace of the object, relative to the connection's base namespace; empty means the connection namespace itself. Segments are separated by "/", without leading or trailing slash. Immutable: it cannot be added, changed or removed after creation. Example: team-a/apps
Constraintspattern: ^[A-Za-z0-9_-][A-Za-z0-9._-]*(/[A-Za-z0-9_-][A-Za-z0-9._-]*)*$
length: <=256
statusobjectnostatus is the observed state of the enforcement; `id` holds the OpenBao enforcement ID.
status.acquiredstringnoHow the operator came to own the object: Created (it created it) or Adopted (it took over an existing one). Empty until owned.
status.conditions[]objectnoCurrent state as conditions: Ready (the OpenBao object matches the spec) and Synced (the last reconcile succeeded), each with a reason such as Available, Drifted, Conflict, ConnectionNotReady or PermissionDenied, and the generation it describes.
Constraintslist type: map (keys: type)
status.conditions[]objectnoCondition contains details for one aspect of the current state of this API Resource.
status.conditions[].lastTransitionTimestring (date-time)yeslastTransitionTime 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.
status.conditions[].messagestringyesmessage is a human readable message indicating details about the transition. This may be an empty string.
Constraintslength: <=32768
status.conditions[].observedGenerationinteger (int64)noobservedGeneration 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.
Constraintsvalue: >=0
status.conditions[].reasonstringyesreason 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.
Constraintspattern: ^[A-Za-z]([A-Za-z0-9_,:]*[A-Za-z0-9_])?$
length: >=1, <=1024
status.conditions[].statusstringyesstatus of the condition, one of True, False, Unknown.
Constraintsone of: True, False, Unknown
status.conditions[].typestringyestype of condition in CamelCase or in foo.example.com/CamelCase.
Constraintspattern: ^([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])$
length: <=316
status.idstringnoIdentifier OpenBao generated for the object (an entity, group or alias ID, or a mount accessor), for kinds that have one; other resources reference it. Example: 6c9f3e0a-1b2c-4d5e-8f90-123456789abc
status.namespacestringnoAbsolute OpenBao namespace the object was written in; empty means the root namespace. If it later differs from the spec, reconciling stops with reason NamespaceChanged. Example: team-a/apps
status.observedGenerationinteger (int64)noThe metadata.generation of this resource that the operator last reconciled.
status.pathstringnoFull OpenBao API path of the object, including its namespace, as last written; deletion uses it even after the spec changed. Example: team-a/sys/policies/acl/app-read
status.rotationNoncestringnoValue of the resource's rotation nonce when one-time inputs, such as a root credential that OpenBao rotates afterwards, were last sent; changing the nonce in the spec sends them again.
status.serverIDstringnoCluster ID of the OpenBao server the object was acquired on. If the connection later reaches another server, reconciling stops with reason ServerChanged and nothing is written or deleted. Example: 80f7de92-c12e-e960-4754-255c32fc6b53
status.writeOnlyHashstringnoKeyed hash (HMAC-SHA256) of the write-only inputs, such as passwords read from Secrets; a change forces a write. It never contains or reveals the values.