#370 Opening merge qualifier CoS entry using RHDS console changes the entry.
Closed: wontfix None Opened 11 years ago by nkinder.

https://bugzilla.redhat.com/show_bug.cgi?id=806566 (Red Hat Directory Server)

Description of problem:
In RHDS 9.0 merge qualifiers cannot be added using GUI. Creating one using
ldapmodify, and opening the same entry in GUI using "properties" will fallback
to default. example "departmentname override merge-schemes" to "departmentname
override" (advanced properties works fine)

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

How reproducible:
100%

Steps to Reproduce:
1. Create a cos entry and add using ldapadd

dn: cn=indirectCoS,ou=People,dc=example,dc=com
objectClass: top
objectClass: cosSuperDefinition
objectClass: cosIndirectDefinition
objectClass: ldapSubEntry
cosIndirectSpecifier: manager
cosAttribute: departmentNumber override merge-schemes
cn: indirectCoS


2. Open RHDS console using 389-console, Open the cos entry in GUI using
properties, & then go to Attributes & click OK

3. Check using ldapsearch cos attribute will be changed to "departmentnumber
override"

Actual results:

dn: cn=indirectCoS,ou=People,dc=example,dc=com
objectClass: top
objectClass: cosSuperDefinition
objectClass: cosIndirectDefinition
objectClass: ldapSubEntry
cosIndirectSpecifier: manager
cosAttribute: departmentNumber override
cn: indirectCoS


Expected results:

dn: cn=indirectCoS,ou=People,dc=example,dc=com
objectClass: top
objectClass: cosSuperDefinition
objectClass: cosIndirectDefinition
objectClass: ldapSubEntry
cosIndirectSpecifier: manager
cosAttribute: departmentNumber override merge-schemes
cn: indirectCoS


Additional info:

The reason is there is no GUI ability to add merge qualifiers, so opening a
entry using GUI will fall it back to default override.

- Either there should be a GUI ability to add merge qualifiers

set default ticket origin to Community

Added initial screened field value.

Do we support operational override merge-schemes?

Replying to [comment:5 rmeggins]:

Do we support operational override merge-schemes?

According to the Red Hat docs, you would only use "override merge-schemes", and in the console code you can not set "operational override". It has to be one or the other, or the console would only display override. Maybe that's another bug? The docs make it look like you can only use one qualifier as well.

The code is a little harder to tell. Looks like you use merge-schemes with other qualifiers, and you can have multiple qualifiers. If this is the case, we would have to rewrite the console mechanism(use check boxes for all the qualifiers & options). I think that is out of the scope for this fix, but I can easily add "operational merge-schemes", etc.

To be consistent with the docs I think we should keep the existing fix, but I have no problem changing the fix.

Ok, so you can use merge-schemes with all the qualifiers, so I am proposing these new drop-down menu options:

"qualifier-default"
"qualifier-default-merge-schemes" -> same as just having "merge-schemes" without a qualifier
"qualifier-override"
"qualifier-override-merge-schemes"
"qualifier-operational"
"qualifier-operational-merge-schemes"
"qualifier-operational-default"
"qualifier-operational-default-merge-schemes"

Note, it does not appear you can use multiple qualifiers.

git push origin master
Counting objects: 19, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (10/10), 1.52 KiB, done.
Total 10 (delta 5), reused 0 (delta 0)
To ssh://git.fedorahosted.org/git/389/ds-console.git
7c3d88a..c83af3b master -> master

move closed tickets to 1.3.0.a1

Metadata Update from @rmeggins:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.3.0.a1

7 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/370

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

3 years ago

Login to comment on this ticket.

Metadata