I disagree -- Do we really want this information to be case insensitive?

I will get consensus from other members of the group.

Per email discussions, we agree that userids should not be case-insensitive, and therefore this works as intended.

Resolving ticket as WONTFIX.

If userids should not be case-insensitive as in comment 2, why the following behavior?

[root@sigma dogtag]# pki -d /opt/rhqa_pki/certs_db -n OCSP3_adminV -c Secret123 -h sigma.lab.eng.rdu.redhat.com -p 30044 ocsp-user-add a1 --fullName=a1

Added user "a1"

User ID: a1
Full name: a1
[root@sigma dogtag]# pki -d /opt/rhqa_pki/certs_db -n OCSP3_adminV -c Secret123 -h sigma.lab.eng.rdu.redhat.com -p 30044 ocsp-group-member-add Administrators a1

Added group member "a1"

User: a1
[root@sigma dogtag]# pki -d /opt/rhqa_pki/certs_db -n OCSP3_adminV -c Secret123 -h sigma.lab.eng.rdu.redhat.com -p 30044 ocsp-user-add A1 --fullName=A1
ConflictingOperationException: Entry already exists.

[root@sigma dogtag]# pki -d /opt/rhqa_pki/certs_db -n OCSP3_adminV -c Secret123 -h sigma.lab.eng.rdu.redhat.com -p 30044 ocsp-user-show A1

User "A1"

User ID: a1
Full name: a1
[root@sigma dogtag]# pki -d /opt/rhqa_pki/certs_db -n OCSP3_adminV -c Secret123 -h sigma.lab.eng.rdu.redhat.com -p 30044 ocsp-user-show a1

User "a1"

User ID: a1
Full name: a1

Per CS/DS Meeting of 06/01/2015: 10.2.5 (needs investigation)

Per CS/DS meeting of 06/08/2015: 10.2.6

I pushed a fix in a277f2740398a5574f9b4da46e869b05fef17a18.

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1633

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, and we apologize for any inconvenience.