Bonjour, Pourriez-vous svp me désinscrire. Adresse mail = [email protected]
Merci, -----Message d'origine----- De : [email protected] [mailto:[email protected]] De la part de [email protected] Envoyé : vendredi 2 juillet 2010 12:00 À : [email protected] Objet : Glpi-user Digest, Vol 58, Issue 2 Send Glpi-user mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://mail.gna.org/listinfo/glpi-user or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Glpi-user digest..." Today's Topics: 1. Re: Why can't mixed case attributes be used in LDAP synchronisation? (Walid Nouh) ---------------------------------------------------------------------- Message: 1 Date: Thu, 01 Jul 2010 19:32:54 +0200 From: Walid Nouh <[email protected]> Subject: Re: [Glpi-user] Why can't mixed case attributes be used in LDAP synchronisation? To: Liste de diffusion des utilsateurs de GLPI <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" Hi, The restriction is due to the php ldap library which send the data back in lower case. Walid. On 01/07/2010 10:40, Paul Reinerfelt wrote: > Hi! > > I am trying to set up LDAB authentication against a Mac OS X Server > Open Directory (which is based on OpenLDAP). Everything works fine for > the attributes that are lower-case but not for the rest (and most of > the relevant attributes are mixed case in Apple's schema, like > 'firstName', 'telephoneNumber', etc.) > > I found a page on the wiki that says that the attributes *must* be > lower case but no explanation as to why, which is weird as mixed case > attributes are perfectly legal in LDAP. I did try to find an answer in > the archives but since there is no search function I only manually > searched as far back as through 2007. I also tried to locate the > restriction in the code but didn't have much success. > > Can anyone enlighten me as to why this restriction exists in GLPI? And > is there anything that can be done to work around it? > > *P** ESS Scandinavia is committed to reducing its environmental > footprint. Please consider whether you really need to print this email*!** > *-----------------------------------------------------------* > *Paul Reinerfelt* > System Administrator > European Spallation Source Scandinavia (ESSS) > > Address: > ESS Scandinavia > Lunds University > P.O.Box 117 > SE-221 00 Lund > (Visiting adress: Stora Algatan 4) > > Phone/Mobile: +46 (0)46 222 88 60 > SMS/MMS: +46 (0)76 133 33 89 > E-mail: [email protected] <mailto:[email protected]> > Home page: http://www.esss.se <http://www.esss.se/> > > > > > > > > _______________________________________________ > Glpi-user mailing list > [email protected] > https://mail.gna.org/listinfo/glpi-user > -------------- next part -------------- An HTML attachment was scrubbed... URL: /public/glpi-user/attachments/20100701/edc2d71a/attachment.htm ------------------------------ _______________________________________________ Glpi-user mailing list [email protected] https://mail.gna.org/listinfo/glpi-user End of Glpi-user Digest, Vol 58, Issue 2 **************************************** _______________________________________________ Glpi-user mailing list [email protected] https://mail.gna.org/listinfo/glpi-user
