#860 user-add --email with i18n characters throws LDAP error
Closed: migrated 3 years ago by dmoluguw. Opened 10 years ago by aakkiang.

# pki -d /opt/rhqa_pki/certs_db                    -n CA_adminV                    -c redhat123                     user-add --fullName=test --email='negyvenkettő' u31
PKIException: LDAP error (21): error result

This is due to LDAP syntax checking. The attribute used for storing e-mail addresses does not support non-ASCII characters. Internationalized e-mail addresses are still not widely supported, so this is really a corner case.

I think all we should do here at this point is to catch the exception and print a nicer error message.

Adding a userid with i18n shows PKIException: LDAP error (19) : error result

# pki -d /opt/rhqa_pki/certs_db                    -n ROOTCA_adminV                    -c Secret123    -h qeblade3.rhq.lab.eng.bos.redhat.com                    -p 30044                     ca-user-add --fullName=test 'ÉricTêko'
PKIException: LDAP error (19): error result

Expected Result :: User friendly error message

Per Offline Triage of 11/30/2016-12/01/2016: FUTURE - minor

Metadata Update from @aakkiang:
- Issue set to the milestone: FUTURE

7 years ago

Metadata Update from @mharmsen:
- Custom field feature adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: None
- Issue priority set to: major (was: minor)
- Issue set to the milestone: 10.5 (was: FUTURE)

6 years ago

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

6 years ago

Metadata Update from @mharmsen:
- Issue assigned to edewata

6 years ago

Per 10.5.x/10.6 Triage: FUTURE

RHBZ: CLOSED UPSTREAM

Metadata Update from @mharmsen:
- Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1232047)
- Issue set to the milestone: FUTURE (was: 10.6)

6 years ago

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

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata