Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1057054

Summary: [RFE][AAA] Provide a way to configure manged authentication domains from the webadmin
Product: [Retired] oVirt Reporter: Allon Mureinik <amureini>
Component: ovirt-engine-configAssignee: Yair Zaslavsky <yzaslavs>
Status: CLOSED DEFERRED QA Contact: bugs <bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.4CC: acathrow, alonbl, bazulay, emesika, gklein, iheim, oourfali, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-21 10:46:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1076964    

Description Allon Mureinik 2014-01-23 12:18:14 UTC
Authentication provides are currently configured via command line. E.g., 

${OVIRT_ENGINE}/bin/engine-managed-domains -action add -domain my.domain.com -user myadmin -provider rhds -interactive

Have a screen to configure these providers /inside the webadmin/ would hold several benefits:
1. Single management console - everything is done from the webadmin
2. No need for shell access to the engine's machine
3. better GUI (although this is a taste issue, I guess)

Comment 1 Allon Mureinik 2014-01-23 13:24:11 UTC
An additional advantage:
4. No need to restart engine in order for the added/edited/remvoed domain to take effect.

Comment 2 Alon Bar-Lev 2014-03-16 21:31:00 UTC
I am unsure I agree that this should be done as adding domains is something that is done very rarely, investing UI resources, localization, backend for one/two time during lifecycle is something I would have avoided.

Comment 3 Alon Bar-Lev 2014-07-21 10:46:37 UTC
the new mechanism of adding provider within the engine is file based, per my comment#2, I think that such configuration are easier for admin and provisioning products using files and not within application or api as it requires interaction with product. I am closing this for now, if you disagree, please reopen.