Hello Jerome,
Thanks for your reply. My case is a little bit different. Our
authentication process is not as simple as collecting and validating
user credentials. For example user can choose authentication via mobile
phone infrastructure. In this case user provides his phone number,
external system sends him a SMS message. User must send a response SMS
message and external system then sends us user details in a case of
successful authentication. In a time between these two SMS messages our
system must display screen with info that authentication process is in
progress.
I see there two non usual things for CAS:
1. Authentication in progress screen
2. CAS should provide CAS client user details because there is no way
to get this info after authentication
At the moment I don't see how to do this without modifying CAS login web
flow.
regards,
Marius
On 2011.07.25 10:43, Jerome LELEU wrote:
Hello,
You can create your own AuthenticationHandler and register it in
deployConfigContext.xml.
We did this to authenticate through another SSO system with a form : our CAS
custom AuthenticationHandler posts the user credentials to the form of the
another SSO system through an HTTP request, retrieves HTTP headers and cookies
of the other SSO system, processes these information and adds some cookies to
the CAS response.
Regards,
Jerome
--
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
