authMethodCreateLdap is a command that creates a new auth method that will be able to authenticate using LDAP.
| Name | Type | Description | Notes |
|---|---|---|---|
| accessExpires | Long | Access expiration date in Unix timestamp (select 0 for access without expiry date) | [optional] |
| allowedClientType | List<String> | limit the auth method usage for specific client types [cli,ui,gateway-admin,sdk,mobile,extension] | [optional] |
| auditLogsClaims | List<String> | Subclaims to include in audit logs, e.g "--audit-logs-claims email --audit-logs-claims username" | [optional] |
| boundIps | List<String> | A CIDR whitelist with the IPs that the access is restricted to | [optional] |
| deleteProtection | String | Protection from accidental deletion of this object [true/false] | [optional] |
| description | String | Auth Method description | [optional] |
| expirationEventIn | List<String> | How many days before the expiration of the auth method would you like to be notified. | [optional] |
| forceSubClaims | Boolean | if true: enforce role-association must include sub claims | [optional] |
| genKey | String | Automatically generate key-pair for LDAP configuration. If set to false, a public key needs to be provided [true/false] | [optional] |
| gwBoundIps | List<String> | A CIDR whitelist with the GW IPs that the access is restricted to | [optional] |
| json | Boolean | Set output format to JSON | [optional] |
| jwtTtl | Long | Jwt TTL | [optional] |
| name | String | Auth Method name | |
| productType | List<String> | Choose the relevant product type for the auth method [sm, sra, pm, dp, ca] | [optional] |
| publicKeyData | String | A public key generated for LDAP authentication method on Akeyless in base64 or PEM format [RSA2048] | [optional] |
| token | String | Authentication token (see `/auth` and `/configure`) | [optional] |
| uidToken | String | The universal identity token, Required only for universal_identity authentication | [optional] |
| uniqueIdentifier | String | A unique identifier (ID) value should be configured for OAuth2, LDAP and SAML authentication method types and is usually a value such as the email, username, or upn for example. Whenever a user logs in with a token, these authentication types issue a "sub claim" that contains details uniquely identifying that user. This sub claim includes a key containing the ID value that you configured, and is used to distinguish between different users from within the same organization. | [optional] |