Anyone have any pointers on this? Or at least a pointer to the
documentation on the web flow stuff? It seems navigating through the
JASIG CAS pages to some documentation is not possible, or at least not
easy/intuitive.
Thanks.
Le 2011-11-01 14:33, Trenton D. Adams a écrit :
I guess what I was really looking for is a way of making sure the
handlers get run again. I used the wrong lingo too, they aren't
technically authentication handlers, they are just handlers.
In the login-webflow.xml, I'm doing this...
<action-state id="realSubmit">
<evaluate
expression="authenticationViaFormAction.submit(flowRequestContext,
flowScope.credentials, messageContext)" />
<transition on="warn" to="warn" />
<transition on="success" to="performAUOnLoginChecks" />
<transition on="error" to="viewLoginForm" />
</action-state>
<action-state id="performAUOnLoginChecks">
<evaluate expression="performAUOnLoginChecksAction" />
<transition on="success" to="sendTicketGrantingTicket" />
</action-state>
Is there a way of having those run during authentication, AND during any
redirection to the service, AND store information in the session for
later retrieval?
The current scenario might be...
1. challenge question not setup
2. redirect to password manager
3. user hits back button to CAS
4. cas redirects directly to service rather than the same as #2
If there's comprehensive docs on this web flow stuff as well, I can
start there, and ask more questions later. I don't want to waste
someone's time. :P
Thanks.
Le 2011-10-31 21:06, Scott Battaglia a écrit :
The result of a successful authentication is the generation of a TGT,
which
is already stored by the CAS server. What else are you looking for?
On Mon, Oct 31, 2011 at 7:30 PM, Trenton D.
Adams<[email protected]>wrote:
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<http://www.ja-sig.org/wiki/display/JSG/cas-user>
--
Trenton D. Adams
Senior Systems Analyst/Web Software Developer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!
--
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
