[DOCS-6065] Automation Configuration API endpoint leaves out auth Created: 20/Aug/15  Updated: 08/Jun/17  Resolved: 08/Jun/17

Status: Closed
Project: Documentation
Component/s: Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andrew Davidson Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.opsmanager.mongodb.com/current/reference/api/automation-config/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.155 Safari/537.36
Referrer: https://docs.opsmanager.mongodb.com/current/reference/cluster-configuration/
Screen Resolution: 1440 x 900
repo: REPONAME
source: reference/api/automation-config


Participants:
Days since reply: 6 years, 36 weeks, 2 days ago
Epic Link: C/OM Update API
Story Points: 0.3

 Description   

Note that auth settings can be configured via API as described here:
https://github.com/10gen-labs/mms-api-examples/tree/master/automation/#example-and-details

These settings have some important nuance: e.g. when adding a new user, a password must be specified in the clear (initPwd). Subsequent requests for the Automation configuration will return the hashed pwd.

This is covered in Authentication



 Comments   
Comment by Michael Benoit [ 05/Jun/17 ]

No, this isn't related to the Users Resource, he's talking about the Automation Config Resource. That said, I'm not clear on what's needed here. andrew.davidson, can you elaborate?

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