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

Bug 2018101

Summary:	cockpit : impossible to create credentials or aliases for replication monitoring synchronization report
Product:	Red Hat Directory Server	Reporter:	sgouvern
Component:	cockpit-389-ds	Assignee:	Simon Pichugin <spichugi>
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	medium	Docs Contact:	Evgenia Martynyuk <emartyny>
Priority:	unspecified
Version:	12.0	CC:	abobrov, emartyny, ldap-maint, mreynolds, spichugi
Target Milestone:	---
Target Release:	dirsrv-12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	redhat-ds-12-9000020211123032220.032d475b	Doc Type:	Bug Fix
Doc Text:	.Configuring credentials and naming aliases for the replication topology report now works correctly in the web console Previously, you could not set the credentials or naming aliases for the replication topology report using the web console because fields in the pop-up windows `Add Report Credentials` and `Add Report Alias`, where you needed to enter the required information, were not writable. In this release, the fields in the pop-up windows are writable, and you can set the report credentials, or configure the naming aliases as expected.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-18 15:28:06 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 sgouvern 2021-10-28 09:10:43 UTC

Description of problem:
In Monitoring / replication tab, Synchronization report :
clicking on 'Add credentials' or 'Add Alias' makes 'Add Report Credentials' or 'Add Report Alias' popup windows open, but even if clicking on one field in these windows makes the field appear as writable, it's impossible to enter any character
The same editing one of the existing connections in 'Replication Report Credentials' section, it's impossible to change any field.

Version-Release number of selected component (if applicable):
cockpit-389-ds-2.0.10-1.module+el9dsrv+12668+daa4c88c.noarch

How reproducible:
always

Steps to Reproduce:
1. Go to 'Monitoring' / 'Replication' / 'Synchronization report' tab
2. On 'prepare report' tab, 'Replication Report Credentials' section, click on 'Add credentials'
3. In the window which opens, click on any of the updatable fields 
4. In the field (which appears as being writable) try to enter characters

Actual results:
It's impossible to write anything

Expected results:
data can be entered and changes can be saved

Additional info:

Same behavior in 'Replication Report Credentials' section, when editing one of the existing connection.
Same behavior too in 'Replica Naming Aliases' section, with 'Add alias' button

Comment 5 sgouvern 2022-02-17 13:14:08 UTC

With cockpit-389-ds-2.0.14-2.module+el9dsrv+14105+a1e450bc.noarch 

Going through the steps described in https://bugzilla.redhat.com/show_bug.cgi?id=2018101#c0
The fields in Monitoring / replication / Prepare report are now writable when adding or editing credentials or aliases.

Marking as VERIFIED

Comment 6 Evgenia Martynyuk 2022-04-20 22:07:29 UTC

Hi Simon, 

can you, please, review the RN candidate in the Doc Text field?

Thanks,
Evgenia

Comment 7 Simon Pichugin 2022-04-22 14:43:53 UTC

I think you need a space (empty line) after the first line. If it's okay like this, ignore my comment.

Otherwise, looks good!

Comment 8 Evgenia Martynyuk 2022-04-22 20:14:39 UTC

Thanks Simon! Added the space

Comment 9 Evgenia Martynyuk 2022-04-25 09:00:25 UTC

Sarka sjanderk kindly agreed to make a peer review. The peer comments are implemented.

Comment 11 errata-xmlrpc 2022-05-18 15:28:06 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-2022:4664