Quoting Geert Bevin: > > On 17-jan-06, at 12:59, Fred Baube wrote: > > >To follow up on my own question ... > > > >>So, then, it is entirely the responsibility of my own > >>CM implementation to devise a mapping between usernames > >>and userid's that both (a) creates unique userid's, and > >>(b) keeps the mapping consistent -- within a particular > >>session -- _across_ calls to verifyCredentials(..) ? > > > >Do I need to do anything to make this mapping available > >to other elements in the Rife authentication framework ? > >In other words, is there any other interface that my CM > >needs to implement, so that other code can map a username > >to a userid, or vice-versa, whenever needed ? > > For the authentication framework to work you need these > (as specified in the javadocs): > > * CredentialsManager > * SessionManager > * SessionValidator
I guess I thought I could write a CM and drop it in without changing anything else, but clearly that won't work unless my new code also implements RoleUsersManager and in effect completely replaces MemoryUsers or DatabaseUsers. The less ambitious alternative is to write a blocking Rep participant which gathers the required authentication info and prepares it for use by the Rep participant that handle authentication (i.e. MemoryUsers or DatabaseUsers). fred -- F.Baube * Georgetown/MSFS/1988 * Think pangalactically. fbaube#saunalahti.fi * Act locally. gsm +358 41 536 8192 * wmd 60°11'10.8"N 24°57'36.9"E _______________________________________________ Rife-users mailing list [email protected] http://www.uwyn.com/mailman/listinfo/rife-users
