AuthType CAS AuthName "CAS" require valid-user Allow from 127.0.0.1 Allow from x.x.x.x/16 Satisfy any
This might work but i havent tried it.IMHO the problem with a second cas auth inside the mod_auth_cas can only be solved by some kind of redirect (rewrite) to some other Location that is not mod_auth_cas protected. The other option would be to implement the "inner" authentication based on the mod_auth_cas authentication (Apache Remote User).
Regards, Joachim Ajey Gore schrieb:
We have few applications hosted inside which are CAS enabled but they do have some anonymous pages when user hits application. This is okay as long as user is inside our network and accessing it from inside. But from outside network, user should not get anonymous content instead should get redirected to CAS page, for this we implemented mod_auth_cas but the problem is that mod_auth_cas is also eating up second service ticket which is issued for underlying application.We want to implement a WebGateway so that if we do not have CAS application, still its protected and if we have CAS enabled application user do not have to sign in again...Any suggestions? Thanks Ajey -- 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
-- Joachim Fritschi Hochschulrechenzentrum (HRZ) L1|01 Raum 248 Petersenstr. 30 64287 Darmstadt Tel. +49 6151 16-5638 Fax. +49 6151 16-3050 E-Mail: [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
