The email is actually not the identifier. The identifier is the userId, and under some circumstance a unoque user can also be identified by the combination of the fields: externalUserId + externalUserType
The rule for the email is as following: It is not possible to sign up with the same id twice. For Administration > Users I am not sure, but my point of view here is basically that an administrator should be have the freedom to do what he wants. But still, you did not give us any steps on what we should do to reproduce it. I mean there are around 5 different possibilities to enter a email. In User Administration, in invitation, in private message center, in sign up. Additionally you can use the SOAP/REST API to enter email addresses or use the LDAP integration to sync emails to our database. Or you can potentially use the Module integration to sync emails to the database. So where exactly did you enter the email ? Btw: There are also situations where the email in the database is NOT unique and it is a desired feature: When you use the OpenMeetings platform standalone AND for example integrated with Moodle (or sugarCRM or whatever). The process is that whenever a external user comes he will be synced to our database. So if a user comes from Moodle or SugarCRM they can have the same email => and that is also okay for us. No need to block anybody, cause in that situation the external user is identified by its externalUserId and externalUserType. So as you see your assumption "email is _always_ unique in the database" is actually not true. It always depends on the type of user. Sebastian 2012/4/19 Hamdi THABET <[email protected]> > What I meant is that the email address must be unique. Adding a new > user with an existing email becomes impossible! > Because the email must be unique within the database as the identifier ID > > > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
