MongoDB LDAP Configuration API
Returns, edits, verifies, and removes LDAP configurations. An LDAP configuration defines settings for MongoDB Cloud to connect to your LDAP server over TLS for user authentication and authorization. Your LDAP server must be visible to the internet or connected to your MongoDB Cloud cluster with VPC Peering. Also, your LDAP server must use TLS. You must have the MongoDB Cloud admin user privilege to use these endpoints. Also, to configure user authentication and authorization with LDAPS, your cluster must run MongoDB 3.6 or higher. Groups for which you have configured LDAPS can't create a cluster using a version of MongoDB 3.6 or lower.
MongoDB LDAP Configuration API is one of 53 APIs that MongoDB publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include LDAP Configuration. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, rate-limit docs, and a changelog.
This API exposes 5 operations across 4 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 2.0.
Requests are made against a single base URL, https://cloud.mongodb.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
MongoDB LDAP Configuration API declares
2 security schemes
for authenticating requests.
It uses HTTP digest authentication (DigestAuth).
It supports OAuth 2.0 (ServiceAccounts) using the clientCredentials flow.
By default, every request must be authenticated.
ServiceAccounts— Learn more about [Service Accounts](https://www.mongodb.com/docs/atlas/api/service-accounts-overview).
Paths & Operations 5
Across 4 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Returns, edits, verifies, and removes LDAP configurations. An LDAP configuration defines settings for MongoDB Cloud to connect to your LDAP server over TLS for user authentication…
Schemas 11
The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are LDAPSecuritySettings (10 properties), LDAPVerifyConnectivityJobRequestParams (7 properties), ApiError (6 properties), LDAPVerifyConnectivityJobRequest (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from MongoDB 12
Other APIs MongoDB publishes across the network.
This is an independent, third-party profile of MongoDB LDAP Configuration API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.