[DOCS-3926] MMS OnPrem 1.5: Document LDAP Auth for web server <-> LDAP Created: 20/Aug/14 Updated: 16/Mar/15 Resolved: 29/Aug/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.10, mms-1.5 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Cailin Nelson | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 24 weeks, 1 day ago | ||||
| Description |
|
The procedure for configuring MMS to talk to a backing MongoDB using LDAP is very similar to MONGODB-CR authentication. The username and password are supplied in the `mongoUri` properties in the properties file. Encrypted credentials are supported in the same way as MONGODB-CR. Adding `authMechanism=PLAIN&authSource=$external` to the URI specifies that these credentials are for LDAP authentication. The following example is in the properties file shipped with MMS:
|
| Comments |
| Comment by Githook User [ 02/Sep/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 02/Sep/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 29/Aug/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 29/Aug/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 27/Aug/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |