tonemcd wrote:
> Again, thanks heaps for making this available - it's done the business
> for me!
Tone,
Awesome! Glad it worked. :)
Brian
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
Brian,
Just a quick note to say *thankyou very much* for making this
available. I installed it into one of my development sites over the
weekend and it works like a charm. I only tried the middleware version
(which is probably more appropriate for an authentication backend) and
found it to work
Alright, I fixed things up a bit and went for the middleware approach.
The CAS module can now intercept all admin interface requests and do
the appropriate authentication routine instead of showing the login
form. Everything can now be configured in settings.py as well so
there's no need to muck
Alright, I'm gonna throw a question out there, maybe someone can help.
As shown above I can intercept the admin index page in order to not
display the login form which doesn't make sense for CAS authentication.
However, this only works if the user needs to be authenticated and
requests the
Quick followup in case anyone is interested (anyone? Bueller?)...
One problem is handling the admin site, which doesn't really account
for an authentication backend that doesn't know the user's password
(making the login form useless). So, without wanting to hack up
django.contrib.admin, here's
Hello Djangonauts,
Just offering my Django implementation of CAS 1.0 authentication
backend in case anyone else is trying to use it. (CAS is a single
sign-on protocol, you can read about it here:
http://www.ja-sig.org/products/cas/index.html) It's a little trickier
to implement than other
6 matches
Mail list logo
