On 08/20/2010 11:03 PM, Dave Kitabjian wrote: > Does anyone know where the "ClientHook" fits in this order-of-execution > sequence?
Seems to be between steps 6 and 7. The global ClientHook runs first and right after that the client specific ClientHook is called. I also noticed that at least with version 4.7, the secret is checked after the hooks run, so the hooks can catch even those requests where the authenticator check fails. So even if the request fails with "Bad authenticator in request from ..." log message, the request would still have been available for processing with ClientHook(s). > *http://open.com.au/radiator/ref.pdf* > > * * > > *1. *Server started > > *2. **StartupHook *called > > *3. *Request received from NAS > > *4. *Global RewriteUsernames applied > > *5. **PreClientHook *called > > *6. *Client clause selected > > *7. *Client RewriteUsernames applied > > *8. *Duplicate detection done > > *9. **PreHandlerHook *called > > *10. *Handler selected > > *11.**PreProcessingHook *called > > *12. *Handler’s RewriteUsername and RewriteFunction applied > > *13. *Session database updated (accounting requests only) > > *14. *Accounting log files (AcctLogFileName and WtmpFileName) written > > *15.**PreAuthHook *called > > *16. *AuthBy clauses invoked > > *17.**PostAuthHook *called > > *18. *Statistics updated > > *19.PostProcessingHook *called (if there is a reply to be sent) > > *Integration* > > > > > > _______________________________________________ > radiator mailing list > radiator@open.com.au > http://www.open.com.au/mailman/listinfo/radiator -- Heikki Vatiainen, Arch Red Oy +358 44 087 6547 _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
