I've solved this by adding a new action state, which transition is based upon 
client address.


Le 13/08/2012 22:06, Philippe MARASSE a écrit :
Folks,

Actually, I've only one authentication scheme, whether the client is from outside or inside our hospital : x509 + login/password fallback.

    Now I have to split this behavior into two parts :
- local clients will have : x509 + spnego first fallback + login/password second fallback
        - external clients will have only : x509 + login/password fallback

The first test I've done with CAS 3.5 SPNEGO works, but I was wondering how to split the behavior upon the origin of the request. Our architecture is pretty classic : 2 Apache frontends (1 internal + 1 external) + 1 Tomcat.

Regards.



--
Philippe MARASSE

Service Informatique - Centre Hospitalier Henri Laborit
BP 587 - 370 avenue Jacques Coeur
86021 Poitiers Cedex
Tel : 05.49.44.57.19


Attachment: smime.p7s
Description: Signature cryptographique S/MIME

Reply via email to