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

Bug 2030884

Summary: [RFE] Web Console: Report Credentials and Report Aliases are not saved when the web console is reloaded
Product: Red Hat Directory Server Reporter: Evgenia Martynyuk <emartyny>
Component: cockpit-389-dsAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: LDAP QA Team <idm-ds-qe-bugs>
Severity: medium Docs Contact: Evgenia Martynyuk <emartyny>
Priority: medium    
Version: 12.0CC: bsmejkal, idm-ds-dev-bugs, mreynolds
Target Milestone: DS12.3Keywords: FutureFeature, Triaged
Target Release: dirsrv-12.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sync-to-jira
Fixed In Version: redhat-ds-12-9030020230711000312-1674d57 Doc Type: Enhancement
Doc Text:
.You can now save credentials and aliases for a replication report using the Directory Server web console Previously, when you used the web console to set credentials and aliases for a replication monitoring report, these settings were no longer present after the web console reload. With this enhancement, when you set the credentials and aliases for the replication report, Directory Server saves new settings in the `.dsrc` file and the web console uploads saved settings after the reload.
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-21 15:13:16 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:

Description Evgenia Martynyuk 2021-12-09 23:47:07 UTC
Description of problem:
It would be good If replication Report Credentials and Report Aliases that were set via the web console would be saved from cash.  

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1.In the web console go to Monitoring -> Replication
2. Set additional Report Credentials (Add Credentials button) or set Report Aliases (Add Aliases button).
3. Generate or refresh replication monitoring report
4. Reload the web console.

Actual results:
You have to edit Report Credentials and Report Aliases again after the web console is reloaded

Expected results:
The replication report uses the Report Credentials and Aliases which were set before.
 

Additional info:
The problem can be solved if:
The problem can be solved if:
1) The browser cache is used to save the data
2) The dsrc file is used when the Replication Monitor Report page is loaded
3) Maybe the button or checkbox "use dsrc file data" are added

Comment 1 mreynolds 2021-12-10 02:02:04 UTC
Using the browser cache is not a good idea, but reading it in from the .dsrc file is.  Especially since the .dsrc file already supports this IIRC.

Comment 2 Evgenia Martynyuk 2022-01-11 19:18:38 UTC
Small update after the discussion with Mark. 

As Add Credentials button in the UI and [repl-monitor-connections] section in the .dsrc file represent the same feature, It would be nice If:

1) UI could update .dsrc file values
2) Values in the .dsrc were loaded to the UI if they are not empty.

Comment 3 Evgenia Martynyuk 2022-01-11 19:32:32 UTC
Corrected.

Small update after the discussion with Mark. 

As Add Credentials and Add Aliases buttons in the UI and [repl-monitor-connections], [repl-monitor-aliases] sections in the .dsrc file represent the same feature, It would be nice If:

1) UI could update .dsrc file values
2) Values in the .dsrc were loaded to the UI.

Comment 4 mreynolds 2023-04-24 18:12:39 UTC
Upstream ticket:

https://github.com/389ds/389-ds-base/issues/5738

Comment 5 mreynolds 2023-04-28 14:36:09 UTC
*** Bug 2190454 has been marked as a duplicate of this bug. ***

Comment 10 bsmejkal 2023-09-20 14:13:14 UTC
Build tested:
389-ds-base-2.3.6-4.module+el9dsrv+19950+6ff0d0d4.x86_64

Checking the connection and aliases manually in WebUI saves the settings to .dsrc

...
[repl-monitor-aliases]
m1 = server.example.com:636

[repl-monitor-connections]
test = server.example.com:636:cn=Directory Manager:password
...

Running tests:
============================================================================================================ test session starts =============================================================================================================
platform linux -- Python 3.9.18, pytest-7.4.2, pluggy-1.3.0 -- /usr/bin/python3
cachedir: .pytest_cache
389-ds-base: 2.3.6-4.module+el9dsrv+19950+6ff0d0d4
nss: 3.90.0-3.el9_2
nspr: 4.35.0-3.el9_2
openldap: 2.6.3-1.el9
cyrus-sasl: 2.1.27-21.el9
FIPS: disabled
rootdir: /mnt/tests/rhds/install/389-ds-base/dirsrvtests
configfile: pytest.ini
plugins: base-url-2.0.0, playwright-0.4.2
collected 2 items                                                                                                                                                                                                                            

dirsrvtests/tests/suites/clu/dsrc_test.py::test_dsrc PASSED                                                                                                                                                                            [ 50%]
dirsrvtests/tests/suites/clu/dsrc_test.py::test_dsrc_repl_mon PASSED                                                                                                                                                                   [100%]

============================================================================================================= 2 passed in 24.73s =============================================================================================================


Marking as VERIFIED.

Comment 11 Evgenia Martynyuk 2023-11-20 17:05:24 UTC
RN text passed all reviews

Comment 13 errata-xmlrpc 2023-11-21 15:13:16 UTC
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 (redhat-ds:12 bug fix and enhancement update), 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-2023:7429