#1419 pki group-member-show should be case insensitive
Closed: Duplicate Opened by mharmsen.

pki group-member-show should be case insensitive

Steps to Reproduce:

# pki -d /opt/rhqa_pki/certs_db -n CA_adminV -c redhat123
user-add user123 --fullName=new
Added user "user123"
    User ID: user123 Full name: new
# pki -d /opt/rhqa_pki/certs_db -n CA_adminV -c redhat123
group-member-add group1 user123
Added group member "user123"
    User: user123
# pki -d /opt/rhqa_pki/certs_db -n CA_adminV -c redhat123
group-member-show group1 USER123 ResourceNotFoundException?: Group member
USER123 not found
# pki -d /opt/rhqa_pki/certs_db -n CA_adminV -c redhat123
group-member-show group1 user123
Group member "user123"
    User: user123

Actual results:

group-member-show is case sensitive

Expected results:

group-member-show should be case insensitive

Additional info:

# 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
# 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
# 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.
# 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
# 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/15/2015: 10.3

Duplicate of #1069, which was fixed in a277f2740398a5574f9b4da46e869b05fef17a18

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.3.0

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/1980

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.

Metadata