[DOCS-1818] Document setup and limitations of backup agent when running in an environment with --auth Created: 16/Aug/13  Updated: 11/Jan/17  Resolved: 10/Sep/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Task Priority: Major - P3
Reporter: David Hows Assignee: Allison Reinheimer Moore
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 10 years, 23 weeks, 1 day ago

 Description   

Document setup and limitations of backup agent when running in an environment with --auth

Currently we collect credentials prior to performing initial sync. This is not documented.

Currently there is no way to alter credentials once initial sync is completed, this is also not documented.



 Comments   
Comment by auto [ 10/Sep/13 ]

Author:

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

Message: minor: edits for DOCS-1818
Branch: master
https://github.com/10gen/mms-docs/commit/829e3fd5074a7f9afeda9b7625e676a534ac3a1b

Comment by auto [ 10/Sep/13 ]

Author:

{u'username': u'schmalliso', u'name': u'schmalliso', u'email': u'allison.moore@10gen.com'}

Message: DOCS-1818: documenting backup setup for MongoDB with auth
Branch: master
https://github.com/10gen/mms-docs/commit/be2cc061c6be57ccf73d935042ecf321b2357c75

Comment by David Hows [ 20/Aug/13 ]

The limitations and suggestions around auth will need to be documented early on in the setup process.

Providing this as an after thought when they have logged in and already existing user is counter productive.

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