Thank you Mike for your answer. I started this topic, because i have an assignment at my Faculty, which requires connection between Django and an LDAP (assistant insisted on 389ds). I installed Django, enabled admin, logged in through Firefox. I can't make up my mind, do i need to connect Django and LDAP like so that all users from LDAP can login through e.g. localhost:8000/admin, or do i need to make a register/login page, where users from LDAP server can login and onlu admin can login from admin page? The second is mpre logical to me, but i don't know, because i am new to Django and Python.
On Tue, Sep 11, 2012 at 12:36 AM, Mike Dewhirst <mi...@dewhirst.com.au>wrote: > On 11/09/2012 4:14am, Tony wrote: > >> Hi everybody, >> >> I am new to Django and Python, and right now, i am going through the >> documentation. I have an assignment at my Faculty, where i need to >> install Django, 389ds LDAP server (where i have to store my users) and i >> need to somehow connect them two, so i can auth users from LDAP when >> logging into Django. i have read some documentation, and i saw a massive >> lines of code, add this, add that, and i don't get any of that. >> > > I think the best first step is to tightly specify your requirements. There > are lots of different approaches and your choice of available open source > depends a lot on what you want to do. For example, you may be interested in > ldap group membership being related to Django groups. > > Being new to Python and Django isn't a problem. Look at Mark Pilgrim's > Dive into Python (the first one which covers Python 2.x) then do the Django > tutorials up to the point where the Django Admin is working for you. That > will demonstrate "add this, add that" and make it easier for you. Also, > install pip for fetching this and that! > > The Django Admin auth will happily/easily accept external auth backends. > > I have stopped using ldap nowadays but when I had it working the general > principle employed was to query the ldap server and if it authenticated the > offered userid and password AND the userid didn't exist in the Django user > table, the backend inserted a new record. > > From my own experience I can recommend you start with a plan to unit test > absolutely everything. The ldap side of things is tricky. Once you get your > head around Python and Django you will really appreciate the nth degree of > flexibility. > > Good luck > > Mike > > > >> Can someone please help me with this issue, i'll be very grateful. >> >> Thank you >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Django users" group. >> To view this discussion on the web visit >> https://groups.google.com/d/**msg/django-users/-/**7ArlkeKjY0YJ<https://groups.google.com/d/msg/django-users/-/7ArlkeKjY0YJ> >> . >> To post to this group, send email to django-users@googlegroups.com. >> To unsubscribe from this group, send email to >> django-users+unsubscribe@**googlegroups.com<django-users%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/**group/django-users?hl=en<http://groups.google.com/group/django-users?hl=en> >> . >> > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to django-users+unsubscribe@** > googlegroups.com <django-users%2bunsubscr...@googlegroups.com>. > For more options, visit this group at http://groups.google.com/** > group/django-users?hl=en<http://groups.google.com/group/django-users?hl=en> > . > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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.
