Bug 1374314 - explicit required permissions for the Ansible provider user
Summary: explicit required permissions for the Ansible provider user
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation
Version: 5.6.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: GA
: 5.7.0
Assignee: Red Hat CloudForms Documentation
QA Contact: Red Hat CloudForms Documentation
URL:
Whiteboard: doc
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-08 12:31 UTC by Colin Arnott
Modified: 2018-04-04 04:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-04 04:41:55 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description Colin Arnott 2016-09-08 12:31:15 UTC
Document URL: 
https://access.redhat.com/documentation/en/red-hat-cloudforms/4.1/managing-providers/#adding_an_ansible_tower_provider

Section Number and Name: 
2.2.1.5 Adding an Ansible Tower Provider: credentials

Describe the issue: 
The Ansible provider currently provides no requirements for privilege level on the authenticating user, my security standards prevent me from giving cart blanch access to my Ansible environment. Can you please enumerate the permissions required by CFME so that I can use least privilege when creating the CFME user for my Ansible environment.

Suggestions for improvement: 
Add a section indicating required permissions for the Ansible provider.

Additional information:

Comment 3 Andrew Dahms 2016-10-31 01:03:03 UTC
Moving to the default assignee for triaging.

Raising needinfo against Brandon for comment #2.

Comment 7 Andrew Dahms 2018-04-04 04:41:55 UTC
Thank you for raising this bug.

After further discussion with the program team, we have been given the advice not to document specific permissions for service accounts at this time based on the following article -

http://cloudformsblog.redhat.com/2017/08/16/security-management-operations/

As such, I will be closing this bug for now, but we can re-investigate this request again in the future if required.


Note You need to log in before you can comment on or make changes to this bug.