Hi Matthias, the userId uniquely identifies a user for the authentication framework in RIFE. This is what will be used by the authentication managers to create an authentication session ID and be able to tie that back to the same user.
The username and password are used for authorization. They're both needed in the RoleUsersManager to ensure that a user is valid and known. This authorization layer is entirely pluggable and in the case of the RoleUsersManager it is based on username, password and allowed roles. The long userId is what ties the authorization layer to the authentication layer. Hope this makes sense. Best regards, Geert On 21 May 2008, at 11:47, Matthias Barmeier wrote: > > Hi, > > I am a bit confused about some methods in the RoleUsersManager > interface. I have implemented a new CredentialManager that implements > the CredentialsManager and the RoleUsersManager interfaces. > > This works perfect for my database application. I now tried to > implement > a really simple role based authorization layer for another project and > noticed that some methods in RoleUsersManager deals with long typed > userId and others needs a String typed user name. > > Shouldn't the user name be "unique enough"? Are there rife magic to > avoid the long typed userId because I retrieve userdata from a legacy > system that has no numerical id. > > Ciao > Matthias > > > -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rife-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rife-users?hl=en -~----------~----~----~----~------~----~------~--~---
