[SERVER-12891] --saslServiceName isn't in mongos Created: 25/Feb/14 Updated: 10/Dec/14 Resolved: 05/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sam Kleinman (Inactive) | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
probably should be |
| Comments |
| Comment by Shaun Verch [ 05/Mar/14 ] |
|
That is correct. saslServiceName is only settable via setParameter unless you are using the new YAML config file from |
| Comment by Andy Schwerin [ 05/Mar/14 ] |
|
There is no - |
| Comment by Andy Schwerin [ 04/Mar/14 ] |
|
samk, I think this is a docs ticket. There is no --saslServiceName option in mongos or mongod. There's a --setParameter saslServiceName=<>, IIRC. sverch, do you recall differently? |
| Comment by Rui Zhang (Inactive) [ 26/Feb/14 ] |
|
saslServiceName can be configured with --setParameter ./mongodb/bin/mongos --setParameter=authenticationMechanisms=GSSAPI --setParameter=saslServiceName="mongoservice" --configdb=~/dbs/ |