Hide Forgot
Description of problem: The server returns an HTTP 422 response when creating a user if UTF-8 characters are provided for that user's login, firstname or lastname. Note that other types of interesting characters are allowed, such as latin-1 and CJK. Version-Release number of selected component (if applicable): The following software is installed: * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.23-1.el6_5.noarch * candlepin-common-1.0.1-1.el6_5.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.9.23-1.el6_5.noarch * candlepin-tomcat6-0.9.23-1.el6_5.noarch * elasticsearch-0.90.10-6.el6sat.noarch * foreman-1.6.0.46-1.el6sat.noarch * foreman-compute-1.6.0.46-1.el6sat.noarch * foreman-gce-1.6.0.46-1.el6sat.noarch * foreman-libvirt-1.6.0.46-1.el6sat.noarch * foreman-ovirt-1.6.0.46-1.el6sat.noarch * foreman-postgresql-1.6.0.46-1.el6sat.noarch * foreman-proxy-1.6.0.30-1.el6sat.noarch * foreman-selinux-1.6.0.14-1.el6sat.noarch * foreman-vmware-1.6.0.46-1.el6sat.noarch * katello-1.5.0-30.el6sat.noarch * katello-certs-tools-1.5.6-1.el6sat.noarch * katello-default-ca-1.0-1.noarch * katello-installer-0.0.64-1.el6sat.noarch * katello-server-ca-1.0-1.noarch * openldap-2.4.23-32.el6_4.1.x86_64 * pulp-katello-0.3-4.el6sat.noarch * pulp-nodes-common-2.4.1-0.7.beta.el6sat.noarch * pulp-nodes-parent-2.4.1-0.7.beta.el6sat.noarch * pulp-puppet-plugins-2.4.1-0.7.beta.el6sat.noarch * pulp-puppet-tools-2.4.1-0.7.beta.el6sat.noarch * pulp-rpm-plugins-2.4.1-0.7.beta.el6sat.noarch * pulp-selinux-2.4.1-0.7.beta.el6sat.noarch * pulp-server-2.4.1-0.7.beta.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch How reproducible: _Almost_ always. Steps to Reproduce: 1. Create a user via the API. Provide any number of UTF-8 characters as a login, firstname or lastname. Actual results: HTTP 422 response with one of the following messages: * First name is invalid * Last name is invalid * Surname is invalid Expected results: One of the following: * A user is created. * A helpful error message is returned. Additional info: Once in a while - say, once every 20 attempts - a user is sucessfully created even though UTF-8 chars are submitted.
Created attachment 939027 [details] Server log for the described error.
A test targeting this issue has been created. See: https://github.com/SatelliteQE/robottelo/pull/1403
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Created redmine issue http://projects.theforeman.org/issues/7548 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/7548 has been closed ------------- Anonymous Applied in changeset commit:f4aa6463dc217aa2739927997a51254988ad929f.
moving fixed intems into 6.2
The following permutations were used to verify this issue: Login | First Name | Surname ----------------------------- überüser | Bart Simpson mane | Zé | Mane rolo | Ze | Mané 㳤沪㛴懎镶歿宓퓺헍艁 | 㳤沪㛴懎镶歿 | 宓퓺헍艁 * All users were successfully created via the web UI * All users were able to successfully log in via the web UI Next step, we will check this issue using the REST API.
API Verified on: Satellite6.2.0 Snap4.0 running on RHEL 7 x86_64 Steps: * Use curl to call the /api/users API endpoint * Create a user for each variant on table (see below) * Login via the web UI using each user curl -X POST -H "Content-Type: application/json" -H "Authorization: Basic KEY" -d '{ "user": { "login": "USER", "firstname": "FIRST", "lastname": "LAST", "mail": "bart@simpson.com", "password": "s3cr3tâé", "auth_source_id": 1 } }' "https://SATELLITE_HOST/api/users" The above was tested for each variant below: Login | First Name | Surname ----------------------------- überüser | Bart Simpson mane | Zé | Mane rolo | Ze | Mané 㳤沪㛴懎镶歿宓퓺헍艁 | 㳤沪㛴懎镶歿 | 宓퓺헍艁 Result: * All users were successfully created via the REST API (curl & postman) * All users were able to successfully log in via the web UI
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-2016:1500