On 3/10/06, Matt <[EMAIL PROTECTED]> wrote:
>
> OK, I was confused about why Django still needs usernames in its
> database even though LDAP is the new authentication method. I thought
> it would require authenticating via LDAP, then checking for the user
> _and_ pass in Django's database. I did
OK, I was confused about why Django still needs usernames in its
database even though LDAP is the new authentication method. I thought
it would require authenticating via LDAP, then checking for the user
_and_ pass in Django's database. I didn't realize that I will only
have to copy the username
>Another issue that would create problems is
>adding users to LDAP directly -- Django wouldn't know about those users
Yes, but you create the user in django on login attempts to django
sites.
If LDAP auth successfukl:
search user DB
if not found:
add usert to db based on ldap pertmissi
Sure that would work, but it sounds like a lot of work, and it's
duplicating a lot of data. Another issue that would create problems is
adding users to LDAP directly -- Django wouldn't know about those users.
--~--~-~--~~~---~--~~
You received this message becaus
> If it was my decision I'd simply use Django's authentication.
> Unfortunately it's my supervisor's decision, and he wants me to use
> LDAP _exclusively_ so that's what I have to do.
>
> I don't know much about LDAP, but from what I understand users can be
> grouped based on their level of access
If it was my decision I'd simply use Django's authentication.
Unfortunately it's my supervisor's decision, and he wants me to use
LDAP _exclusively_ so that's what I have to do.
I don't know much about LDAP, but from what I understand users can be
grouped based on their level of access. For exam
Whats the problem with faking a user ?
I would reccomend during you LDAP auth code you simple create a user in
django.users if it doesnt already exit. This can be compeltly
transparent to the user, they will never know.
I tend to like to have to setup users to my small admin sites, cause
everyon
Is there any good documentation for implementing LDAP with Django?
The admin feature of Django is awesome and I'd love to use it, but in
addition to the need for LDAP my app will have to parse uploaded CSV
files in order to populate certain database tables simply because there
is far too much dat
Joseph,
Here is a link to the rails+lap wiki entry:
http://wiki.rubyonrails.com/rails/pages/HowtoAuthenticateViaLdap
-- Nick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to t
On 3/7/06, Matt <[EMAIL PROTECTED]> wrote:
>
> I've read about a 'hack' Jason Huggins posted a month ago. He
> implements LDAP support for his Django app, but it requires every user
> to be in both LDAP and the user database table. This seems pointless
> to me. Either you use Django's built-in
I've read about a 'hack' Jason Huggins posted a month ago. He
implements LDAP support for his Django app, but it requires every user
to be in both LDAP and the user database table. This seems pointless
to me. Either you use Django's built-in database authentication or you
use LDAP, not both.
I
11 matches
Mail list logo
