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 <jlmurph...@gmail.com> wrote: > 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 system, packages it into an OpenToken, and then forwards > it on to another system. The target system only accepts OpenToken for > SSO. > > My Django application doesn't need to store User information nor > authenticate the user. It is just a translator between one identity > assertion and the other. The end-user won't even know they hit my > Django app as their HTTP requests will just pass right through via > redirects. It's just magic to them. > > I am already porting the perl module to python but am running into > issues with the KeyGenerator class. Luckily the original devs provided > plenty of good tests so I know when I am on the right track. I hope to > open source the code once I am done. > > Thanks, > 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 group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
