On Sun, Dec 21, 2008 at 8:00 PM, Sahil R Cooner wrote:
> You don't have to store anything in the database you can just use the models
> to store
> information then return that the user is authenticated...I can post a code
> example for you I
> have made using ldap auth without storing to a data
I have the same issue, but my issue is that Django is interfacing with
a web service and ideally will have *no user database* on the front
end. All the examples I've seen involve essentially copying the user
from LDAP/wherever and sticking them in the User model, which:
a) Is duplication across s
Have you read this -
http://docs.djangoproject.com/en/dev/topics/auth/#other-authentication-sources?
On Mon, Dec 1, 2008 at 19:02, Devye <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am trying to integrate a Django app with an in-house developed
> webapp. The biggest hurdle is to consolidate the two
Hi,
I am trying to integrate a Django app with an in-house developed
webapp. The biggest hurdle is to consolidate the two sets of users
data and session mechanism. I was wondering if it is easy in Django to
customize the authentication logic and session logic? If so, how would
I go about it?
I d
4 matches
Mail list logo
