----- "Vidar Ramdal" <[email protected]> wrote: > On Tue, Oct 27, 2009 at 10:47 PM, Carl F. Hall > <[email protected]> wrote: > > Is there a plug point for performing actions post authentication? > My scenario is that we'll have a CAS authentication > > handler that after a user passes through successfully we'll need to > get the user's information (profile type stuff) from > > the enterprise directory that doesn't live in JCR. Some circles > call this user provisioning after authentication. > > Thoughts? > > What kind of profile information are you going to fetch, and what are > you using it for? > If you're just going to display user information, this sounds like a > job you could do while rendering the request, and as such, you > wouldn't have to mess with the authentication stuff. > You have the name of the current authenticated user available in the > SlingHttpServletRequest object.
For now, just general profile information. This information won't live in JCR and has to be pulled from our central enterprise directory. I was thinking of having something that would run just once at the beginning of a session. I don't really want to tie this to authentication but would like to have a place to hook in just after authentication. It needs to be before anything in the system that needs user information has a chance to start. > -- > Vidar S. Ramdal <[email protected]> - http://www.idium.no > Sommerrogata 13-15, N-0255 Oslo, Norway > + 47 22 00 84 00 / +47 21 531941, ext 2070
