Hi Guys,
We have authentication handlers for CAS that do a variety of things.
One of them is ensuring password requirements, another is to ensure
challenge question/response is setup, etc. If any of these checks fail,
we redirect to our password manager utility. To do this, we modify the
web flow in the context, and change the redirect to include our password
manager, and we pass the password manager a service URL to redirect to
after everything is complete.
Once at the password manager utility, having been CAS authenticated, the
user can press the back button, and skip the auth-handlers. CAS just
sees the ticket, and sends them on their way.
How would I go about storing the authentication handler "results" so
that they can be used from within the CAS session, so that the back
button doesn't allow them to proceed to the service, but instead runs a
piece of code which modifies the web flow again?
I wasn't the one that implemented the new CAS 3 stuff, so I'm a bit in
the dark as to the details of how all this works. They basically ported
all of my changes to the old CAS 2, forward to the new CAS 3.
Any help or direction to appropriate documentation would be greatly
appreciated.
Thanks.
--
Trenton D. Adams
Senior Systems Analyst/Web Software Developer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!
--
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---
--
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-user
