On Sun, Jun 29, 2008 at 11:31 AM, spacetaxi <[EMAIL PROTECTED]> wrote:
> Additionally I'd implement a "authentication bridge" between the > different apps to share the login information with django. This is the only part I've had any experience with. We have a legacy PHP app that we are rewriting in Django, but which still does the vast majority of the work across the application. It's pretty simple to get Django and PHP to share the same session information once a user has been logged in on the PHP side. That said, we do not have the ability yet to create an authenticated Django "user" to be used in the Django apps. We sort of have to crib in stuff from the session. So, we've lost any of the auth and perm stuff that Django does. That means custom login_required decorators and a custom perms system. It's not ideal, but a transitional thing, it works. I can provide more details on the session sharing if you wish. /alex --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
