---
title: "POST /create-auth-method-ldap"
method: POST
path: "/create-auth-method-ldap"
tags: ["v2"]
---

# POST /create-auth-method-ldap

`POST /create-auth-method-ldap`

## Request body

- CreateAuthMethodLDAP — createAuthMethodLDAP is a command that creates a new auth method that will be able to authenticate using LDAP. [Deprecated: Use auth-method-create-ldap command]
  - `access-expires` integer — Access expiration date in Unix timestamp (select 0 for access without expiry date)
  - `allowed-client-type` string[] — limit the auth method usage for specific client types [cli,ui,gateway-admin,sdk,mobile,extension]
  - `audit-logs-claims` string[] — Subclaims to include in audit logs, e.g "--audit-logs-claims email --audit-logs-claims username"
  - `bound-ips` string[] — A CIDR whitelist with the IPs that the access is restricted to
  - `delete_protection` string — Protection from accidental deletion of this object [true/false]
  - `description` string — Auth Method description
  - `expiration-event-in` string[] — How many days before the expiration of the auth method would you like to be notified.
  - `force-sub-claims` boolean — if true: enforce role-association must include sub claims
  - `gen-key` string — Automatically generate key-pair for LDAP configuration. If set to false, a public key needs to be provided [true/false]
  - `gw-bound-ips` string[] — A CIDR whitelist with the GW IPs that the access is restricted to
  - `json` boolean — Set output format to JSON
  - `jwt-ttl` integer — Jwt TTL
  - `name` string, required — Auth Method name
  - `product-type` string[] — Choose the relevant product type for the auth method [sm, sra, pm, dp, ca]
  - `public-key-data` string — A public key generated for LDAP authentication method on Akeyless in base64 or PEM format [RSA2048]
  - `token` string — Authentication token (see `/auth` and `/configure`)
  - `uid-token` string — The universal identity token, Required only for universal_identity authentication
  - `unique-identifier` 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.

## Response `200`

createAuthMethodLDAPResponse wraps response body.

- CreateAuthMethodLDAPOutput
  - `access_id` string
  - `prv_key` string

## Other responses

- `default` — errorResponse wraps any error to return it as a JSON object with one "error" field.

---

[API](https://skmtc.net/akeyless/apis/akeyless-api.md) · [All operations](https://skmtc.net/akeyless/apis/akeyless-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/akeyless/akeyless-api/versions/0ceb25634501/schema)