As I've said in a previous post, the audit filter does absolutely nothing but populate a thread local w/ the current user info. This thread local is used by the audit hook and audit portlet when posting audit messages, and these pieces are all in EE.
What you need is not the auditing mechanism at all. All you need to do is implement a LoginPostAction class that does what you're asking. Something along the lines of:
1public class MyLoginPostAction extends Action {
2
3 public void run(HttpServletRequest req,HttpServletResponse resp) throws ActionException {
4 try {
5 User user = PortalUser.getUser(req);
6 // write user info to the target file
7 } catch (Exception e) {
8 throw new ActionException(e);
9 }
10 }
11}
Add this guy to the portal.properties file for the hook:
1login.events.post=com.example.MyLoginPostAction
Done.
Please sign in to flag this as inappropriate.
