[DOCS-3806] When non-default SaslServiceName is used in server, Clients connecting need to specify this Created: 23/Jul/14  Updated: 16/Mar/15  Resolved: 17/Oct/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.12

Type: Improvement Priority: Major - P3
Reporter: Peter Garafano (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:
Days since reply: 9 years, 18 weeks ago

 Description   

If starting mongod using a non-default security.sasl.serviceName, the mongo shell (and any drivers) will need to specify the new service name. This should be made clear in the docs anywhere the saslServiceName is mentioned.

The documentation currently lacks any mention of the --gssapiServiceName parameter for mongo.exe.

Pages that need an update (best guess)

  1. http://docs.mongodb.org/manual/reference/program/mongo/
  2. http://docs.mongodb.org/manual/tutorial/control-access-to-mongodb-with-kerberos-authentication/
  3. http://docs.mongodb.org/manual/reference/configuration-options/#security.sasl.serviceName

I suspect there are driver pages that will also need updating.



 Comments   
Comment by Githook User [ 15/Oct/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-3806: Add gssapiServiceName, gssapiHostName

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/617597aee02f54554ada306bb73ecfbafafdf217

Generated at Thu Feb 08 07:46:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.