Well that doesn't seem like much fun! But you're right, that's what
will eventually happen.
-Justin
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this gro
Well since that is the case, why even use Django? Why not just do
this conversion/forwarding using the existing Perl OpenToken library
and deploy it to a cgi-bin?
-Matteo
On Jan 7, 2:17 pm, Justin wrote:
> Matteo,
>
> Thanks for the response. I wish I could just use the
> django.contrib.auth au
Matteo,
Thanks for the response. I wish I could just use the
django.contrib.auth authentication mechanisms and be done with this.
However, I am not looking to use OpenToken to authenticate users in
Django, per se.
I will be making a Django app that accepts an authentication assertion
from another
I don't understand why you would need to use this for server-side
authentication in the Django environment? So this OpenToken Single
Sign-on appears to be more similar to Django's own
django.contrib.auth, and django.contrib.sessions packages, and
possibly even less secure (and less documented) tha
Hello group,
Does anybody have experience with the OpenToken specification? It is
an authentication token that some (not many) applications use for SSO.
I found existing Perl module that encrypts and decrypts the token but
I need a Python version to use in a Django project. Not much luck
finding
5 matches
Mail list logo
