I am using the django-cas implementation: https://github.com/KTHse/django-cas2
Pretty sure that's what we used for integration with a small internal Django utility app. I recall fighting with URL mappings a bit but got it working in the end. This is against CAS 3.5.2, but it should work with any CAS 3.x version.
in my django application i have the following settings: CAS_SERVER_URL= 'https://xxx.xxxx.com:8443/cas-server-webapp-3.5.2/' CAS_SERVICE_URL='http://localhost:8000' CAS_LOGOUT_COMPLETELY=True CAS_SINGLE_SIGN_OUT=True CAS_RENEW=False CAS_GATEWAY=False CAS_REDIRECT_URL='/homePage' CAS_IGNORE_REFERER=False CAS_RETRY_LOGIN=False CAS_AUTO_CREATE_USERS=False CAS_EXTRA_LOGIN_PARAMS=None CAS_PROXY_CALLBACK=None
You MUST use an https URL for your application (CAS_SERVICE_URL) for single sign-on to work.
and i have the following url mapped: url(r'^dologin/$', 'django_cas.views.login'), url(r'^dologout/$', 'django_cas.views.logout')
You'll have to analyze and troubleshoot your URL mappings as they are entirely application specific.
which redirect me the cas authentification page , after that i'm being redirected to my homePage but i'm receiving a ' HTTP 403 error forbidden' , and the following url: http://localhost:8000/dologin/?next=%2FhomePage&ticket=ST-1-CxrtTYycarg3d9XNbhXo-cas01.example.org
Sounds like a ticket validation problem. Turning up django-cas logging helped me troubleshoot integration problems. I should note that the URL above is http, where it should be https. While many folks attempt to get up and running quickly without SSL, it invariably causes more problems rather than simplifying.
M -- 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
