> -----Original Message----- > From: Mark St.Godard [mailto:[EMAIL PROTECTED] > ... > The AuthenticationProvider err.. provides a layer ontop of > the actual authenticatonDao, so maybe I am missing something.
Hi Mark! Hmmm, it could be me that's been missing it. In my case where I need to hit several DBs, it sounds like I should have instead turned my AuthenticationServiceImpl into AuthenticationProviderImpl (implementing AuthenticationProvider) and get away from Acegi's DaoAuthenticationProvider & AuthenticationDao interfaces altogether. Am I close? To answer your curiosity, our first data source is a reference DB for a user's identity, like whether they're active or terminated, an employee or non-employee, if they're hourly or exempt from overtime, etc. The second DB contains a person's access roles that make sense to couple with the lifecycle of DB #2's records. The third DB contains area management responsibilities and the app's audit log (which we insert into upon every authentication event). A fourth DB will be connected soon that is our fingerprint and background check reference DB. Who knows how many more we may add in the future... :-) Scott ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Home: http://acegisecurity.org Acegisecurity-developer mailing list Acegisecurity-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
