Bug 1425935
Summary: | [RFE] Add SSO client command line registration tool | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Ravi Nori <rnori> |
Component: | AAA | Assignee: | Ravi Nori <rnori> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Gonza <grafuls> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | future | CC: | bgraveno, bugs, lsvaty, mgoldboi, mperina, pstehlik, rmeggins, ylavi |
Target Milestone: | ovirt-4.2.0 | Keywords: | FutureFeature |
Target Release: | 4.2.0 | Flags: | 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
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. Verified with: ovirt-engine-4.2.1.1-0.1.el7.noarch 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. |