[DOCS-2339] update enable authentication tutorial Created: 03/Dec/13  Updated: 16/Mar/15  Resolved: 20/Feb/14

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

Type: Task Priority: Major - P3
Reporter: Sam Kleinman (Inactive) Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates DOCS-2338 Please document procedure to remove a... Closed
Participants:
Days since reply: 9 years, 51 weeks, 6 days ago

 Description   

http://docs.mongodb.org/manual/tutorial/enable-authentication/

  • improve introduction to provide a little context, link to security concepts documentation.
  • create h2 at the end for "next steps" to link to related tutorials (creating users, querying users, assinging users to roles, etc.)
  • remove "query users from this tutorial"
  • use new style sequences
  • add procedure for disabling authentication.
  • retitle and rename document to reflect "managing authentication" rather than just enabling.
  • add appropriate redirects.


 Comments   
Comment by Githook User [ 20/Feb/14 ]

Author:

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

Message: DOCS-2339: edits mostly for parallelism, and no-op steps formating
Branch: master
https://github.com/mongodb/docs/commit/b1027b52f180d4444cdad1bdc7ad9e82a948f63f

Comment by Githook User [ 20/Feb/14 ]

Author:

{u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}

Message: DOCS-2339 enable auth: add second tutorial

Signed-off-by: Sam Kleinman <samk@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/b269c57428a930e507055620f917f4d729130ad5

Comment by Githook User [ 20/Feb/14 ]

Author:

{u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}

Message: DOCS-2339 enable authentication on a mongodb instance

Signed-off-by: Sam Kleinman <samk@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/b5f0dd3da92a7411fbe0087c09be8d49b1bade12

Comment by Githook User [ 04/Feb/14 ]

Author:

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

Message: DOCS-2339: edits to structure
Branch: master
https://github.com/mongodb/docs/commit/f2b3b14e462cef5f3f6fbf0be4bcaaae1620564a

Comment by Gregor Macadam [ 03/Dec/13 ]

Copied from DOCS-2338

Yes, this is very much essential.

I was trying for back out plan, in that I enable the authentication in mongodb and modified application so that it will get authenticated before performing any operations on the database side.

But, what if the this whole procedure fails, we need to put that back to normal working. As per my understand, I thought of restarting mongodb without authentication ( that is not to include keyFile option) though is fine but not documented and then remove the admin database (remember i have added all database users to admin database ) or remove database users.But, I stick to remove database user from admin database.

Also when we add users to database and not running mongodb in authentication mode, connecting from script will give warning message before it writes. It doesn't fail to write, rather it warns.

Regards,
Srinivasa

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