Bug 1425935

Summary: [RFE] Add SSO client command line registration tool
Product: [oVirt] ovirt-engine Reporter: Ravi Nori <rnori>
Component: AAAAssignee: Ravi Nori <rnori>
Status: CLOSED CURRENTRELEASE QA Contact: Gonza <grafuls>
Severity: medium Docs Contact:
Priority: medium    
Version: futureCC: bgraveno, bugs, lsvaty, mgoldboi, mperina, pstehlik, rmeggins, ylavi
Target Milestone: ovirt-4.2.0Keywords: FutureFeature
Target Release: 4.2.0Flags: rule-engine: ovirt-4.2+
grafuls: testing_plan_complete+
mgoldboi: planning_ack+
mperina: devel_ack+
lsvaty: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Release Note
Doc Text:
This update includes the new ovirt-register-sso-client-tool command-line tool to register SSO clients. When running the tool, the user is prompted to enter the client ID, callback prefix, and the certificate location. A new entry is created in the sso_clients table if one does not exist, or the existing one with the same client ID is updated. The client_secret which is written to a temporary file should be noted and used by the client. The client secret in the sso_clients table is encrypted and is for SSO internal use only.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-12 10:11:44 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: 1416491, 1506077    

Description Ravi Nori 2017-02-22 19:51:04 UTC
Add command line tool for registration of third party sso clients.

Comment 1 Red Hat Bugzilla Rules Engine 2017-11-22 08:01:46 UTC
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 2 Gonza 2018-01-29 10:15:33 UTC
Verified with:
ovirt-engine-4.2.1.1-0.1.el7.noarch

Comment 3 Sandro Bonazzola 2018-02-12 10:11:44 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.