[DOCS-11879] Add security.ldap.validateLDAPServerConfig to Server documentation Created: 16/Jul/18  Updated: 30/Oct/23  Resolved: 17/Dec/19

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Shakir Sadikali Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 1
Labels: ldap, settings
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.opsmanager.mongodb.com/current/reference/configuration/#authentication-through-ldap


Issue Links:
Depends
Related
is related to SERVER-32933 Allow mongod to start when unable to ... Closed
Participants:
Days since reply: 4 years, 2 weeks, 2 days ago
Epic Link: DOCSP-1769
Story Points: 0.3

 Description   

 

security.ldap.validateLDAPServerConfig is a new MongoDB Server configuration setting used by OpsManager 3.6.5, new for MongoDB 3.4.14 and 3.6.3. However, this config setting does not appear anywhere in the MongoDB Server documentation, and only appears in the changelog and release notes for OpsManager and the Automation Agent. Might be a good idea to add it to the server documentation as well.



 Comments   
Comment by Githook User [ 28/Jan/20 ]

Author:

{'email': 'kay.kim@10gen.com', 'username': 'kay-kim', 'name': 'Kay Kim'}

Message: DOCS-11879: security.ldap.validateLDAPServerConfig
Branch: v3.4
https://github.com/mongodb/docs/commit/42a9ee324bfb5bdbe6de55ca956d93aa0f470157

Comment by Githook User [ 17/Dec/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-11879: security.ldap.validateLDAPServerConfig
Branch: v3.4.24
https://github.com/mongodb/docs/commit/c0daed1a2a1ad9b807b8a10f8ddf3b2af8096709

Comment by Githook User [ 17/Dec/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-11879: security.ldap.validateLDAPServerConfig
Branch: v4.0
https://github.com/mongodb/docs/commit/a90e230cfc613bccf59d884e2ac746098ba23cd9

Comment by Githook User [ 17/Dec/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-11879: security.ldap.validateLDAPServerConfig
Branch: v3.6
https://github.com/mongodb/docs/commit/81466555280dc972652f175a023c3f4d6e756059

Comment by Githook User [ 17/Dec/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-11879: security.ldap.validateLDAPServerConfig
Branch: master
https://github.com/mongodb/docs/commit/5d8aed44e51e7d7022cc7cb4f197447638335f84

Comment by Louisa Berger [ 08/Oct/18 ]

Yes, `validateLDAPServerConfig` is supported. 

For new server commands, we add everything in CM/OM that the server team lists for us in the Server Parameter Changes list for new server releases (https://wiki.corp.mongodb.com/display/KERNEL/4.0+Server+Parameter+Changes). 

Comment by James Broadhead (Inactive) [ 08/Oct/18 ]

1./ I don't know – MongoDB options are owned by the Cloud Automation team
cc: louisa.berger

2./ Our policy is that we should support every MongoDB option. Thanks for calling this to our attention. This would be good to figure out & either file CLOUDP tickets to fix, or to fix the docs so that they list every option.
(another approach would be to avoid documenting all of these fields in both places, relying on our "support every option" policy)

Generated at Thu Feb 08 08:03:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.