python-ldap-dev

python-ldap syncrepl consumer

[Mikkel K. J. <mi...@li...>]

Hi All and Sean Burford

Sean did you ever get your python-ldap consumer to work ?

I was searching the net for a way to update other systems, when my LDAP
changed. I found your attempt to make a python consumer. Do you have any
code, other than want i can find in the maillinglist ?

Thoughts for usability is:

    GConf LDAP proxy/backend
    Kerberos password updater
    OpenAFS user administration 

Med Venlig Hilsen / Kind Regards




Mikkel Kruse
Johnsen
Adm.Dir.

Linet
Ørholmgade 6 st tv
Copenhagen N 2200
Denmark

Work:    +45
21287793
Mobile: +45
21287793
Email:
mi...@li...
IM:
mi...@li...
(MSN)
 Professional
Profile
Healthcare 


Network
Consultant 

Re: python-ldap syncrepl consumer

[Michael S. <mi...@st...>]

Mikkel Kruse Johnsen wrote:
> Sean did you ever get your python-ldap consumer to work ?

I'd also like to know this. But I suspect it's currently not possible due to
http://sourceforge.net/tracker/?func=detail&aid=2829057&group_id=2072&atid=352072

> I was searching the net for a way to update other systems, when my LDAP
> changed. I found your attempt to make a python consumer. Do you have any
> code, other than want i can find in the maillinglist ?

In a customer project we've implemented a short-time polling system querying
OpenLDAP's accesslog database which also leads to quick updates on the target.

Ciao, Michael.

Re: Multiple Email Values

[Chris D. <pa...@ft...>]

On Wed, Dec 30, 2009 at 02:41:03PM +0100, Christoph Holtermann wrote:
> Hello all !
> 
> I have a basic question about data representation in LDAP.
> I know just this list, maybe you can point me to the right one.
> I use LDAP for storing my contacts. I keep thinking about the
> simple case of people having multiple email. One case
> would be to have an attribute "mail" another one "mozillaSecond
> Email". On the other hand I know that it
> is possible to store multiple values in the corresponding LDAP-
> attribute. but i wonder how it could be possible to also store
> an additional information about these email. For example
> Hans Wurst has
> a@b.c "work",
> b@b.c "outdated since 2000"...
> I guess that this is not possible or needs complex modifications.
> Does anybody know something helpful about this ?

You probably want a general LDAP or openldap mailing list for this but...
I'm not subscribed to one either :-).

First take a peek at this from the openldap-software list

http://www.openldap.org/lists/openldap-software/200203/msg00646.html

If you're caring from an MTA perspective...
Postfix's LDAP maps suggest a 'maildrop' attribute for calculating actual
delivery.

And now a suggestion so you can spend an afternoon seeing what it
breaks...
Well, atleast in my LDAP schemas the mail attribute has syntax
1.3.6.1.4.1.1466.115.121.1.15

And looking at 6.10 of RFC2252
http://tools.ietf.org/html/rfc2252

You can put any unicode string there you want to such
as 
Christoph Holtermann Obsolete  <c.h...@fo...r>


-- 
Chris Dukes
"In cynicism she's about 35" -- Terry Pratchett's "Hog Father"

Re: Multiple Email Values

[Michael S. <mi...@st...>]

Chris Dukes wrote:
> On Wed, Dec 30, 2009 at 02:41:03PM +0100, Christoph Holtermann wrote:
>> I use LDAP for storing my contacts. I keep thinking about the
>> simple case of people having multiple email. One case
>> would be to have an attribute "mail" another one "mozillaSecond
>> Email". On the other hand I know that it
>> is possible to store multiple values in the corresponding LDAP-
>> attribute. but i wonder how it could be possible to also store
>> an additional information about these email.
> 
> If you're caring from an MTA perspective...
> Postfix's LDAP maps suggest a 'maildrop' attribute for calculating actual
> delivery.

'maildrop' has a different semantics.

> And now a suggestion so you can spend an afternoon seeing what it
> breaks...
> Well, atleast in my LDAP schemas the mail attribute has syntax
> 1.3.6.1.4.1.1466.115.121.1.15
> 
> And looking at 6.10 of RFC2252
> http://tools.ietf.org/html/rfc2252
> 
> You can put any unicode string there you want to such
> as 
> Christoph Holtermann Obsolete  <c.h...@fo...r>

This is IMO bad advice since MUAs expect only the raw e-mail address in
attribute 'mail' (see section 2.16 in RFC 4524) which also contains some other
interesting notes.

Ciao, Michael.

Multiple Email Values

[Christoph H. <c.h...@gm...>]

Hello all !

I have a basic question about data representation in LDAP.
I know just this list, maybe you can point me to the right one.
I use LDAP for storing my contacts. I keep thinking about the
simple case of people having multiple email. One case
would be to have an attribute "mail" another one "mozillaSecond
Email". On the other hand I know that it
is possible to store multiple values in the corresponding LDAP-
attribute. but i wonder how it could be possible to also store
an additional information about these email. For example
Hans Wurst has
a@b.c "work",
b@b.c "outdated since 2000"...
I guess that this is not possible or needs complex modifications.
Does anybody know something helpful about this ?

regards,

C.Holtermann

Re: Multiple Email Values

[Michael S. <mi...@st...>]

Christoph Holtermann wrote:
> I have a basic question about data representation in LDAP.
> I know just this list, maybe you can point me to the right one.

For general LDAP questions you might find ld...@um... more helpful since
there are more people lurking there.

> I use LDAP for storing my contacts. I keep thinking about the
> simple case of people having multiple email.

Unfortunately this case is not simple.

> One case
> would be to have an attribute "mail" another one "mozillaSecond
> Email". On the other hand I know that it
> is possible to store multiple values in the corresponding LDAP-
> attribute. but i wonder how it could be possible to also store
> an additional information about these email. For example
> Hans Wurst has
> a@b.c "work",
> b@b.c "outdated since 2000"...
> I guess that this is not possible or needs complex modifications.
> Does anybody know something helpful about this ?

The big question is what your LDAP-enabled MUAs or other LDAP clients expect
in the attribute 'mail' or how you can configure the clients used to handle
other attributes etc. E.g. I don't any MUA which handles multiple attribute
values in 'mail' in a smart way. Simply the first value is taken.

I guess at the end you'll find yourself to add separate entries for all e-mail
adresses and office locations.

Ciao, Michael.