Just some more thoughts on this subject. In the DBSecurityService there are two primary keys. The user id and the username (login name). The user id is the primary key for all database purposes but the username is the primary for the SecurityService interface since all methods use this field to identify users. For this reason I think that username should be treated as a primary key and if it needs to be changed it has to be done using an explicit method like 'void renameUser(Usert user, String name)'. Within DBSecurityService would be very easy to change that field. In LDAPSecurityService a new entry con be created with all the same values and the old entry can be deleted.
Any thoughts? -- Humberto > -----Original Message----- > From: Humberto Hernandez Torres > Sent: Tuesday, February 11, 2003 6:28 PM > To: 'Turbine Developers List' > Subject: Changing the username in SecurityService > > > Hey guys, In regards of this defect: > http://scarab.werken.com/scarab/issues/id/TTWS44 > > The username cannot be changed in the LDAPSecurityService because it is > the primary_key for the Users. Neither I think it is a good idea to change > it in DBSecurirtyService using the DBSecurityService:store(User user) > method. However, I understand the need to change the username, but I would > suggest to have a different method 'void renameUser(Usert user, String > name)'. This is consistent with the way many Web pages operate, they let > you change your information in one page but if you want to change your > account name you have to go to a diffferent page. > > The alternative is to restructure the LDAPSecurityService to use a unique > integer id. At this moment I don't know what the implications would be. I > will think about it tonight. > > -- > Humberto > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
