Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #802 (closed defect: invalid)

Opened 13 years ago

Last modified 12 years ago

TG_User's email address is required to be unique

Reported by: aaron.bentley@… Owned by: anonymous
Priority: normal Milestone:
Component: Identity Version: 0.9a5
Severity: normal Keywords:
Cc:

Description

While it might seem like a nice illusion, it's pretty clear that there's no one-to-one relationship between people and email addresses. Many people have more than one address, and many people share an address. Furthermore, one person may legitimately have no email address or multiple accounts on a web site.

For all these reasons, I believe it does not make sense for emailAddress to be an alternate id on TG_User.

Change History

comment:1 Changed 13 years ago by jvanasco@…

there was a whole discussion on this ( i yelled about it the most ), which led to the user class being moved from the identity provider to model.py

make sure that you're running .9a5, and you can define your user as you want in model.py - and you can define your login requirements in app.cfg

comment:2 Changed 13 years ago by jorge.vargas

  • Status changed from new to closed
  • Resolution set to invalid

The identity model you have in model.py is a suggestion, with this new aproach as long as you keep the relationship (group/user/permission) your identity model can be whatever you want without even having to extend the old (and deprecated TG_* classes)

please refer to  http://tinyurl.com/fdypk for the discussion and resolution of this.

Note: See TracTickets for help on using tickets.