Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
+
 Reporter:  spr@…   |Owner:  nobody
 Type:  enhancement |   Status:  closed
Component:  Contrib apps|  Version:  SVN
 Severity:  normal  |   Resolution:  wontfix
 Keywords:  ldap,usernames  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * easy:   => 0


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  s...@mahonri5.net  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:  wontfix   |  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by russellm):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 There's no reason this needs to exist in Django core. We added an
 extension API specifically so people can build external interfaces to
 auth.

 [http://pypi.python.org/pypi/django-auth-ldap/ django-auth-ldap]  is one
 example of an external LDAP implementation.

 Marking wontfix in favor of having a vibrant external project cover this
 need.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  s...@mahonri5.net  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by hejsan):

 * cc: hr.bjarni+dja...@gmail.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=.

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  s...@mahonri5.net  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by wogan):

 * cc: dja...@wogan.id.au (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  s...@mahonri5.net  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Comment (by psagers):

 Replying to [comment:34 psagers]:
 > I've submitted a more complete LDAP authentication backend in [11526],
 complete with full documentation and unit tests. I think we can get it
 into the distribution, but it could use some test coverage.
 >
 > Thanks

 Sorry, make that #11526.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  s...@mahonri5.net  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Comment (by psagers):

 I've submitted a more complete LDAP authentication backend in [11526],
 complete with full documentation and unit tests. I think we can get it
 into the distribution, but it could use some test coverage.

 Thanks

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  s...@mahonri5.net  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by hcarvalhoalves):

 * cc: hcarvalhoal...@gmail.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  s...@mahonri5.net  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by bne):

 * cc: b...@isotoma.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  s...@mahonri5.net  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by nix):

 * cc: listu...@peternixon.net (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  s...@mahonri5.net  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by Guilherme Gondim ):

 * cc: seme...@taurinus.org (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Comment (by spkane):

 Replying to [comment:28 programmerq]:
 > Replying to [comment:26 spkane]:
 > > ldapauth.patch (4.5 kB) - added by spkane on 10/24/08 10:33:11.
 > > This patch is reasonably specific to my needs, but I would bet
 hard money, that this is an issue faced by other people, so a more robust
 version of this patch should likely be considered. The issue is that the
 best thing for me to use as a username within our LDAP implementation is
 the prefix of the email address, since it is the only thing guaranteed to
 be unique (we have many employees with the same name). However, our email
 addresses are, [EMAIL PROTECTED] Django does not allow a period
 in the username, so I added some logic to handle the username (for django)
 and the ldap_username separately and use the proper one in the proper
 place. Basically, the users login as "sean_kane" and the ldap backend
 converts that to "sean.kane" when talking to the ldap server and then uses
 "sean_kane" when talking to the Django server.
 >
 > I'm not sure that's where that kind of logic belongs. I'd be inclined to
 use the cn as the "username" field, and then just tell users to login with
 their e-mail address. I've never implemented that, but I've heard of
 people using the Django auth system in such a way that people can log in
 with their e-mail address instead of their username. You'd basically just
 have to roll your own login forms, and make sure your views don't spit out
 the actual "username"-- they'll just spit out the e-mail address.
 >
 > I've also seen some discussion come up about allowing dots in a
 username. I don't know where that discussion went though. Ultimately the
 decision to include this logic in the ldapbackend will need to come from a
 core dev, but I'm a big fat -1 on the issue.

 I don't really care about it being implemented here, and I'm not the one
 to make such a decision, but I had to do the work and wanted something
 that would not prevent me from upgrading Django so I put it here for
 myself. Since I did the work, I wanted to make it available to others,
 until something is properly designed. If the decision is to remove it from
 here, I would strongly suggest opening up a ticket to handle creating a
 mechanism in the auth framework to handle providing proper mapping of
 usernames used in auth backends with Django usernames.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by programmerq):

  * needs_tests:  0 => 1

Comment:

 Replying to [comment:26 spkane]:
 > ldapauth.patch (4.5 kB) - added by spkane on 10/24/08 10:33:11.
 > This patch is reasonably specific to my needs, but I would bet hard
 money, that this is an issue faced by other people, so a more robust
 version of this patch should likely be considered. The issue is that the
 best thing for me to use as a username within our LDAP implementation is
 the prefix of the email address, since it is the only thing guaranteed to
 be unique (we have many employees with the same name). However, our email
 addresses are, [EMAIL PROTECTED] Django does not allow a period
 in the username, so I added some logic to handle the username (for django)
 and the ldap_username separately and use the proper one in the proper
 place. Basically, the users login as "sean_kane" and the ldap backend
 converts that to "sean.kane" when talking to the ldap server and then uses
 "sean_kane" when talking to the Django server.

 I'm not sure that's where that kind of logic belongs. I'd be inclined to
 use the cn as the "username" field, and then just tell users to login with
 their e-mail address. I've never implemented that, but I've heard of
 people using the Django auth system in such a way that people can log in
 with their e-mail address instead of their username. You'd basically just
 have to roll your own login forms, and make sure your views don't spit out
 the actual "username"-- they'll just spit out the e-mail address.

 I've also seen some discussion come up about allowing dots in a username.
 I don't know where that discussion went though. Ultimately the decision to
 include this logic in the ldapbackend will need to come from a core dev,
 but I'm a big fat -1 on the issue.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Comment (by programmerq):

 I intend to write tests for this patch using the {{{iw.mock.ldap
 module}}}. This is a very low priority project for me. I'll likely work on
 it at/during a sprint-- it'd be nice to finally have included. The patches
 submitted are kind of a mess-- some are patches, some are standalone
 python files.

 This ticket needs to have the docs, new code, and tests in a single patch
 file in order for it to be ready for check-in. I'll do my best to sort
 through the various versions of the patch and see if I can get something
 in the right format. Right now it's a big mess. :)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by spkane):

 * cc: [EMAIL PROTECTED] (added)
  * keywords:  => ldap,usernames

Comment:

 ldapauth.patch (4.5 kB) - added by spkane on 10/24/08 10:33:11.
 This patch is reasonably specific to my needs, but I would bet hard
 money, that this is an issue faced by other people, so a more robust
 version of this patch should likely be considered. The issue is that the
 best thing for me to use as a username within our LDAP implementation is
 the prefix of the email address, since it is the only thing guaranteed to
 be unique (we have many employees with the same name). However, our email
 addresses are, [EMAIL PROTECTED] Django does not allow a period
 in the username, so I added some logic to handle the username (for django)
 and the ldap_username separately and use the proper one in the proper
 place. Basically, the users login as "sean_kane" and the ldap backend
 converts that to "sean.kane" when talking to the ldap server and then uses
 "sean_kane" when talking to the Django server.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Comment (by EvilDMP):

 In order for this not to throw up an error:
 {{{
 Exception Value:
 'dict' object has no attribute 'LDAP_OPTIONS'
 Exception Location:
 /usr/lib/python2.5/site-packages/django/contrib/auth/ldapauth.py in
 authenticate, line 113
 }}}
 line 113 of ldapauth.py:
 {{{
 self.ldap.set_option(k, self.settings.LDAP_OPTIONS[k])
 }}}
 needs to be:
 {{{
 self.ldap.set_option(k, self.settings["LDAP_OPTIONS"][k])
 }}}
 I presume that other instances of that syntax need to be changed.

 Also, the syntax for settings.py that worked for me were:
 {{{
 import ldap
 LDAP_OPTIONS = 'ldap.OPT_X_TLS_DEMAND,1'
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
--+-
 Reporter:  [EMAIL PROTECTED]  |   Owner:  adrian
 Type:  enhancement   |  Status:  new   
 Priority:  normal|   Milestone:
Component:  Contrib apps  | Version:
 Severity:  normal|Keywords:
--+-
 This patch provides a backend that will allow users to authenticate
 against LDAP. It creates User objects based on fields in LDAP.
 
 Various LDAP settings are provided by the projects settings.py file.

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---