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

Bug 1817585

Summary:	Changing the SASL mapping priority prevents to create mapping
Product:	Red Hat Directory Server	Reporter:	sgouvern
Component:	cockpit-389-ds	Assignee:	mreynolds
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	11.0	CC:	lkrispen, spichugi, tbordaz
Target Milestone:	---
Target Release:	dirsrv-11.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.4.2.11-1.module+el8dsrv+6254+69a018e7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-29 08:04:41 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 2020-03-26 15:49:55 UTC

Description of problem:
'SASL settings and mappings' : When creating a new SASL mapping, the 'Create mapping' button becomes available when all parameters values are entered, but becomes unavailable again as soon as 'SASL mapping priority' is modified, preventing to create the new mapping.
From there, there is no other solution than canceling the operation and restarting from scratch  

Version-Release number of selected component (if applicable):
cockpit-389-ds-1.4.2.9-1.module+el8dsrv+6001+1cbc6dcf.noarch

How reproducible:
always

Steps to Reproduce:
1. Go to 'SASL settings and mappings'
2. Click 'create new mapping'
3. Enter values for all parameters
4. Modify the SASL mapping priority

Actual results:
Create mapping button becomes unavailable, preventing the operation to be performed

Expected results:
New SASL mapping is created, with the chosen priority

Additional info:

Comment 3 sgouvern 2020-04-20 07:02:33 UTC

With 
cockpit-389-ds-1.4.2.12-1.module+el8dsrv+6328+f04d7471.noarch
389-ds-base-1.4.2.12-1.module+el8dsrv+6328+f04d7471.x86_64

After modifying the SASL mapping priority, the SASL mapping can now be correctly created, with the chosen priority

=> marking as verified

Comment 5 errata-xmlrpc 2020-04-29 08:04:41 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, 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/RHBA-2020:1961