> Ideally, at least for #2 and #3 above, it would be great to have access to > the LDAP DN and context of the successful authentication. There doesn't > appear to be a way for the authentication handler to release this > information. Any ideas or suggestions as to how this can be done cleanly > and in a way that's easily maintainable with future releases of CAS?
I think it's reasonable to return some metadata about a successful authentication, but I'm curious what you have in mind when you say "context of the successful authentication." A DirContext? For cases where you're dealing with pooled resources, that would mean returning a pooled resource outside the context of the pool manager which would be dangerous at best. Returning a container of information about the successful bind seems a lot safer. I wonder if pre/post authentication hooks might allow you to accomplish your goals. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
