Bug 1654241
| Summary: | Add backend functionality to UI's Server Tab No. 2 (CLI and UI) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Directory Server | Reporter: | Anuj Borah <aborah> | ||||||||||||||
| Component: | cockpit-389-ds | Assignee: | mreynolds | ||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | RHDS QE <ds-qe-bugs> | ||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 11.0 | CC: | afarley, cpelland, lkrispen, mhonek, nkinder, pasik, rmeggins, spichugi, tbordaz, vashirov | ||||||||||||||
| Target Milestone: | DS11.0 | ||||||||||||||||
| Target Release: | dirsrv-11.0 | ||||||||||||||||
| Hardware: | All | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | sync-to-jira | ||||||||||||||||
| Fixed In Version: | 389-ds-base-1.4.1.6-2.module+el8dsrv+3912+aa2ce078.x86_64 | Doc Type: | If docs needed, set a value | ||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2019-11-06 12:42:00 UTC | Type: | Bug | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Embargoed: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Anuj Borah
2018-11-28 10:20:06 UTC
Description of problem: Failed to update attribute: passwordstoragescheme Open cockpit for RHDS. https://rhds-ip-address:9090 > 389 Directory Server > Server Settings > Password Policy > Global Password Policy > Password Storage Scheme > NS-MTA-MD5 > Failed to update attribute: passwordstoragescheme Version-Release number of selected component (if applicable): RHDS 11 How reproducible: Always Steps to Reproduce: 1. Mentioned above 2. 3. Actual results: Failed to update attribute: passwordstoragescheme And server hangs . Expected results: Should take the value . Additional info: Created attachment 1509441 [details]
SS for passwordstoragescheme
Description of problem: Enable Audit Failure Logging button is not working as expected Open cockpit for RHDS. 389 Directory Server > Server Settings > Audit Failure Log Settings . "Enable Audit Failure Logging" button is not working as expected . If you click on "Enable Audit Failure Logging" button , whether it is ticked or not , user can edit Rotation Policy and Deletion Policy. Version-Release number of selected component (if applicable): RHDS 11 How reproducible: Always Steps to Reproduce: 1. Mentioned above 2. 3. Actual results: Enable Audit Failure Logging button is not working as expected Expected results: It should work as expected. Additional info: Created attachment 1509452 [details]
button 1
Created attachment 1509454 [details]
button 2
Description of problem: "Map System User to Database Entry" accepting empty and junk values as input . Open cockpit for RHDS. 389 Directory Server > Server Settings > LDAPI & Autobind Settings > Map System User to Database Entry "Map System User to Database Entry" accepting empty and junk values as input . Version-Release number of selected component (if applicable): RHDS 11 How reproducible: Always Steps to Reproduce: 1. Mentioned above 2. 3. Actual results: Enable Audit Failure Logging button is not working as expected Expected results: It should work as expected. Additional info: Created attachment 1509552 [details]
junk
Created attachment 1509553 [details]
empty
Created attachment 1509555 [details]
empty value
Builds tested: 389-ds-base-1.4.1.9-1.module+el8dsrv+4243+ba0eb3c6.x86_64 cockpit-389-ds-1.4.1.9-1.module+el8dsrv+4243+ba0eb3c6.noarch Backend functionality was added to the tab. Issue from comments #1, #3, #6 are fixed. Marking as VERIFIED. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:3731 |