Package-level declarations
Types
Builder for EntityAliasArgs.
Builder for EntityAlias.
Builder for EntityArgs.
Manages policies for an Identity Entity for Vault. The Identity secrets engine is the identity management solution for Vault.
Manages policies for an Identity Entity for Vault. The Identity secrets engine is the identity management solution for Vault.
Builder for EntityPoliciesArgs.
Builder for EntityPolicies.
Builder for Entity.
Creates an Identity Group for Vault. The Identity secrets engine is the identity management solution for Vault. A group can contain multiple entities as its members. A group can also have subgroups. Policies set on the group is granted to all members of the group. During request time, when the token's entity ID is being evaluated for the policies that it has access to; along with the policies on the entity itself, policies that are inherited due to group memberships are also granted.
Creates an Identity Group Alias for Vault. The Identity secrets engine is the identity management solution for Vault. Group aliases allows entity membership in external groups to be managed semi-automatically. External group serves as a mapping to a group that is outside of the identity store. External groups can have one (and only one) alias. This alias should map to a notion of group that is outside of the identity store. For example, groups in LDAP, and teams in GitHub. A username in LDAP, belonging to a group in LDAP, can get its entity ID added as a member of a group in Vault automatically during logins and token renewals. This works only if the group in Vault is an external group and has an alias that maps to the group in LDAP. If the user is removed from the group in LDAP, that change gets reflected in Vault only upon the subsequent login or renewal operation.
Creates an Identity Group Alias for Vault. The Identity secrets engine is the identity management solution for Vault. Group aliases allows entity membership in external groups to be managed semi-automatically. External group serves as a mapping to a group that is outside of the identity store. External groups can have one (and only one) alias. This alias should map to a notion of group that is outside of the identity store. For example, groups in LDAP, and teams in GitHub. A username in LDAP, belonging to a group in LDAP, can get its entity ID added as a member of a group in Vault automatically during logins and token renewals. This works only if the group in Vault is an external group and has an alias that maps to the group in LDAP. If the user is removed from the group in LDAP, that change gets reflected in Vault only upon the subsequent login or renewal operation.
Builder for GroupAliasArgs.
Builder for GroupAlias.
Creates an Identity Group for Vault. The Identity secrets engine is the identity management solution for Vault. A group can contain multiple entities as its members. A group can also have subgroups. Policies set on the group is granted to all members of the group. During request time, when the token's entity ID is being evaluated for the policies that it has access to; along with the policies on the entity itself, policies that are inherited due to group memberships are also granted.
Builder for GroupArgs.
Manages member entities for an Identity Group for Vault. The Identity secrets engine is the identity management solution for Vault.
Manages member entities for an Identity Group for Vault. The Identity secrets engine is the identity management solution for Vault.
Builder for GroupMemberEntityIdsArgs.
Builder for GroupMemberEntityIds.
Manages member groups for an Identity Group for Vault. The Identity secrets engine is the identity management solution for Vault.
Manages member groups for an Identity Group for Vault. The Identity secrets engine is the identity management solution for Vault.
Builder for GroupMemberGroupIdsArgs.
Builder for GroupMemberGroupIds.
Manages policies for an Identity Group for Vault. The Identity secrets engine is the identity management solution for Vault.
Manages policies for an Identity Group for Vault. The Identity secrets engine is the identity management solution for Vault.
Builder for GroupPoliciesArgs.
Builder for GroupPolicies.
Builder for Group.
Resource for configuring the duo MFA method.
Builder for MfaDuoArgs.
Builder for MfaDuo.
Resource for configuring MFA login-enforcement
Resource for configuring MFA login-enforcement
Builder for MfaLoginEnforcementArgs.
Builder for MfaLoginEnforcement.
Resource for configuring the okta MFA method.
Builder for MfaOktaArgs.
Builder for MfaOkta.
Resource for configuring the pingid MFA method.
Builder for MfaPingidArgs.
Builder for MfaPingid.
Resource for configuring the totp MFA method.
Builder for MfaTotpArgs.
Builder for MfaTotp.
Configure the Identity Tokens Backend. The Identity secrets engine is the identity management solution for Vault. It internally maintains the clients who are recognized by Vault.
Configure the Identity Tokens Backend. The Identity secrets engine is the identity management solution for Vault. It internally maintains the clients who are recognized by Vault.
Builder for OidcArgs.
Manages OIDC Assignments in a Vault server. See the Vault documentation for more information.
Manages OIDC Assignments in a Vault server. See the Vault documentation for more information.
Builder for OidcAssignmentArgs.
Builder for OidcAssignment.
Manages OIDC Clients in a Vault server. See the Vault documentation for more information.
Manages OIDC Clients in a Vault server. See the Vault documentation for more information.
Builder for OidcClientArgs.
Builder for OidcClient.
Builder for OidcKeyAllowedClientIDArgs.
Builder for OidcKeyAllowedClientID.
Builder for OidcKeyArgs.
Builder for OidcKey.
Manages OIDC Providers in a Vault server. See the Vault documentation for more information.
Manages OIDC Providers in a Vault server. See the Vault documentation for more information.
Builder for OidcProviderArgs.
Builder for OidcProvider.
Builder for Oidc.
You need to create a role with a named key. At creation time, the key can be created independently of the role. However, the key must exist before the role can be used to issue tokens. You must also configure the key with the role's Client ID to allow the role to use the key.
You need to create a role with a named key. At creation time, the key can be created independently of the role. However, the key must exist before the role can be used to issue tokens. You must also configure the key with the role's Client ID to allow the role to use the key.
Builder for OidcRoleArgs.
Builder for OidcRole.
Manages OIDC Scopes in a Vault server. See the Vault documentation for more information.
Manages OIDC Scopes in a Vault server. See the Vault documentation for more information.
Builder for OidcScopeArgs.
Builder for OidcScope.