Bug 1654226 - Creating Replication Manager from webui fails if uid=repman is used
Summary: Creating Replication Manager from webui fails if uid=repman is used
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: 389-ds-base
Version: 11.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: DS11.1
: dirsrv-11.1
Assignee: mreynolds
QA Contact: RHDS QE
Marc Muehlfeld
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks: 1843162
TreeView+ depends on / blocked
 
Reported: 2018-11-28 09:58 UTC by Arpit Tolani
Modified: 2020-09-13 22:30 UTC (History)
8 users (show)

Fixed In Version: redhat-ds-11-8020020200604214543.51c5a973
Doc Type: Bug Fix
Doc Text:
Cause: Trying to create a replication manager entry using "uid" as the RDN attribute of the entry Consequence: An error would occur stating you must use "cn" for the attribute value. Fix: Allow "uid" for the entry RDN. Result: The UI and CLI allow both "cn" and "uid" for the RDN of the replication manager entry
Clone Of:
: 1843162 (view as bug list)
Environment:
Last Closed: 2020-07-28 06:55:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
rhds cockpit webui (96.43 KB, image/png)
2018-11-28 09:58 UTC, Arpit Tolani
no flags Details
rhds cockpit webui (219.11 KB, image/png)
2018-11-28 09:59 UTC, Arpit Tolani
no flags Details
verification (95.19 KB, image/png)
2020-07-10 13:42 UTC, Akshay Adhikari
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 4166 0 None closed unable to create replication manager using uid as rdn 2020-11-02 18:14:19 UTC
Red Hat Product Errata RHBA-2020:3171 0 None None None 2020-07-28 06:55:20 UTC

Description Arpit Tolani 2018-11-28 09:58:59 UTC
Created attachment 1509424 [details]
rhds cockpit webui

Description of problem:
Creating Replication Manager from webui fails if uid=repman is used

While creating a replication agreement using webui, If uid=repman is choosed, It fails with error.

[28/Nov/2018:04:44:13.449798112 -0500] conn=70 op=8 ADD dn="uid=repman,cn=config"
[28/Nov/2018:04:44:13.478054359 -0500] conn=70 op=8 RESULT err=65 tag=105 nentries=0 etime=0.0028324086 - attribute "uid" not allowed

cn=repman,cn=config works correctly.

This used to work for older version & lot of customers uses uid=<name> syntax.


Version-Release number of selected component (if applicable):
cockpit-389-ds-1.4.0.19-2.module+el8+1+36e60e1d.noarch
389-ds-base-1.4.0.19-2.module+el8+1+36e60e1d.x86_64
389-ds-base-libs-1.4.0.19-2.module+el8+1+36e60e1d.x86_64


How reproducible:
100%

Steps to Reproduce:
Login to Cockpit Webui
Select Instance
Go to replication
click on Configuration
Add replication manager as uid=<name>


Actual results:
It should work

Expected results:
It fails with error=65, Adding screenshot for more clarity

Additional info:
This was legacy configuration which used to work previously Lot of existing environment uses same convention. It should work for both uid=name & cn=name.

Comment 1 Arpit Tolani 2018-11-28 09:59:31 UTC
Created attachment 1509425 [details]
rhds cockpit webui

Comment 2 mreynolds 2018-11-28 20:47:38 UTC
Yeah lib389 limits this to just cn for replication managers.  I know it will not be easy to change it because of how it's all laid out, but it should be possible.

Comment 3 mreynolds 2020-05-26 12:46:31 UTC
Upstream ticket: 

https://pagure.io/389-ds-base/issue/51113

Comment 8 Akshay Adhikari 2020-07-10 13:42:15 UTC
Created attachment 1700605 [details]
verification

Build tested:

389-ds-base-1.4.2.12-3.module+el8dsrv+6923+6ab1d5c5.x86_64
cockpit-389-ds-1.4.2.12-3.module+el8dsrv+6923+6ab1d5c5.noarch


I can now create a Replication Manager's entry using "uid" as the RDN attribute from the WebUI. Also, replication between instances is working fine.

Marking as VERIFIED.

Comment 10 errata-xmlrpc 2020-07-28 06:55:14 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:3171


Note You need to log in before you can comment on or make changes to this bug.