You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do not understand this request. We are using manageiq with Ansible Tower Provider. We are using an AD user account to log into Ansible Tower from Cloudforms.
Could you please elaborate? What scenario is behind this?
Here are the details we have for this request copied from the original Bugzilla ticke.:
Proposed title of this feature request:
Ability to add Ansible tower as a provider with Active Directory service account
What is the nature and description of the request?:
CloudForms integration with Ansible tower works with the local tower admin credentials, however we need the ability to use an AD service account.
We already have been able to implement SSO with AZURE AD using OAuth2. However it is not able to authenticate with the service accounts from Active directory.
Why do you need this?:
I know in Active Directory exist "user account" and "managed service accounts". As far as I can tell, AD "user accounts" work just fine. So I guess, the user did use an AD "managed service account". I have no idea why anyone would try something like that when you have user accounts working. As far as I know, "managed service accounts" are a nice feature but even in the windows world, it is a rather exotic configuration. There are many applications that do not support "managed service accounts".
I don't have extended access with my BZ account. I only see the message that the BZ was moved to GitHub.
CloudForms integration with Ansible tower works with the local tower admin credentials, this request is for the ability to use an AD service account.
Related Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1715978
The text was updated successfully, but these errors were encountered: