Bug 1249639
| Summary: | changing internal domain to work with the jdbc extension | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Oved Ourfali <oourfali> | |
| Component: | ovirt-engine | Assignee: | Martin Perina <mperina> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ondra Machacek <omachace> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 3.6.0 | CC: | aburden, bazulay, gklein, lsurette, mperina, pstehlik, rbalakri, Rhev-m-bugs, srevivo, ykaul | |
| Target Milestone: | ovirt-3.6.0-rc | |||
| Target Release: | 3.6.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
The provider for the 'internal' user domain has been replaced with the AAA-JDBC extension, which is now installed by default. Upgrading a Red Hat Enterprise Virtualization environment will convert the legacy provider and preserve the 'admin@internal' password. For new installations, the 'admin@internal' password is still set during engine-setup.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1273261 (view as bug list) | Environment: | ||
| Last Closed: | 2016-04-20 01:10:12 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: | 1260573 | |||
| Bug Blocks: | 1273261 | |||
|
Description
Oved Ourfali
2015-08-03 13:05:46 UTC
CodeChange? Or how should be tested? Legacy provider for 'internal', which supports only only one user (admin) and no groups, was replaced with aaa-jdbc provider which supports unlimited number of users and groups same as aaa-ldap provider. So I think that verification should be similar to 1076971: 1. Upgrade for previous version is OK, internal legacy provider is replaced with aaa-jdbc, admin@internal can be logged in with the same password as before 2. New installation is OK, aaa-jdbc is configured properly, admin@internal can be logged in using password specified during engine-setup 3. For both upgrade and new installation verify that user/groups management using ovirt-aaa-jdbc-tool command works correctly Doc text updated so as to be used in the Release Notes. This bug has been cloned, including the old doc text, so that this enhancement can be incorporated into the documentation and tracked. Docs bug: BZ#1273261 |