Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionDjebran Lezzoum
2017-05-25 11:02:23 UTC
Description of problem:
Create/Update user with e-mail address containing extra consecutive dots is allowed
Version-Release number of selected component (if applicable):
* candlepin-2.0.30-1.el7.noarch
* candlepin-selinux-2.0.30-1.el7.noarch
* foreman-1.15.0-0.1.RC2.el7sat.noarch
* foreman-compute-1.15.0-0.1.RC2.el7sat.noarch
* foreman-debug-1.15.0-0.1.RC2.el7sat.noarch
* foreman-ec2-1.15.0-0.1.RC2.el7sat.noarch
* foreman-gce-1.15.0-0.1.RC2.el7sat.noarch
* foreman-installer-1.15.0-0.develop.201703100324gitb570b53.el7sat.noarch
* foreman-installer-katello-3.5.0-1.nightly.201703312206git730de81.el7sat.noarch
* foreman-libvirt-1.15.0-0.1.RC2.el7sat.noarch
* foreman-openstack-1.15.0-0.1.RC2.el7sat.noarch
* foreman-ovirt-1.15.0-0.1.RC2.el7sat.noarch
* foreman-postgresql-1.15.0-0.1.RC2.el7sat.noarch
* foreman-proxy-1.15.0-0.1.RC2.el7sat.noarch
* foreman-rackspace-1.15.0-0.1.RC2.el7sat.noarch
* foreman-selinux-1.15.0-0.1.RC2.el7sat.noarch
* foreman-vmware-1.15.0-0.1.RC2.el7sat.noarch
* katello-3.4.0-1.rc2.el7sat.noarch
* katello-ca-consumer-sat-r220-02.lab.eng.rdu2.redhat.com-1.0-1.noarch
* katello-certs-tools-2.4.0-1.el7sat.noarch
* katello-client-bootstrap-1.3.0-1.el7sat.noarch
* katello-common-3.4.0-1.rc2.el7sat.noarch
* katello-debug-3.4.0-1.rc2.el7sat.noarch
* katello-default-ca-1.0-1.noarch
* katello-installer-base-3.5.0-1.nightly.201703312206git730de81.el7sat.noarch
* katello-selinux-3.0.2-1.el7sat.noarch
* katello-server-ca-1.0-1.noarch
* katello-service-3.4.0-1.rc2.el7sat.noarch
* openldap-2.4.40-13.el7.x86_64
* pulp-client-1.0-1.noarch
* pulp-docker-plugins-2.3.0-1.git.0.02c948c.el7sat.noarch
* pulp-katello-1.0.2-1.el7sat.noarch
* pulp-puppet-plugins-2.12.1-1.git.0.1aeb10f.el7sat.noarch
* pulp-puppet-tools-2.12.1-1.git.0.1aeb10f.el7sat.noarch
* pulp-rpm-plugins-2.12.1-1.el7sat.noarch
* pulp-selinux-2.12.1-1.git.0.b41b7ba.el7sat.noarch
* pulp-server-2.12.1-1.git.0.b41b7ba.el7sat.noarch
* python-ldap-2.4.15-2.el7.x86_64
* tfm-rubygem-ldap_fluff-0.4.6-1.el7sat.noarch
* tfm-rubygem-net-ldap-0.15.0-1.el7sat.noarch
How reproducible:
Always
Steps to Reproduce:
1.hammer user create --firstname="fSqPgRGpBY" --lastname="ALnULfJpKo" --mail="dot..dot" --login="user" --password="password" --auth-source-id="1"
2.
3.
Actual results:
The user is created
Message,Id
User [user] created,373
Expected results:
[ERROR 2017-05-25 05:47:12 API] 422 Unprocessable Entity
[ERROR 2017-05-25 05:47:12 Exception] Email address is invalid
Could not create the user:
Email address is invalid
Additional info:
The current behavior is reproducible in UI also, and also allow to update the user data with this invalid e-mails
invalid e-mails examples that are invalid and allow the user to be created/updated:
email@example..c
dot..dot
dot...dot@example....com