> Hi all! > > I'm playing around with StatusNet at the moment- I'm curious whether > microblogging might improve communication and "up-to-dateness" at > work ;-) > > Since I wanted to integrate everything into our AD the new LDAP plugin > came in handy. But the README is wrong: > > $config['ldap']['nickname_attribute'] > $config['ldap']['nickname_email'] > $config['ldap']['nickname_fullname'] > $config['ldap']['nickname_homepage'] > $config['ldap']['nickname_location'] > > should read: > > $config['ldap']['nickname_attribute'] > $config['ldap']['email_attribute'] > $config['ldap']['fullname_attribute'] > $config['ldap']['homepage_attribute'] > $config['ldap']['location_attribute'] > > shouldn't it?
Yep - you're completely right, and I'll fix that. Thanks for noticing! > However, if I understand the code correctly you're mapping LDAP > attributes to StatusNet attributes only the first time someone logs in > and only when autoregister is true. Wouldn't it be possible to get some > attributes (like email) always from our AD and only the others (like > bio) from the StatusNet DB? > > I don't want people to change, for example, their email address since > the "official" one should be used. Similarly, I want AD changes (like a > location change) to show up on StausNet. Yes, you're right again! We're working on authentication/authorization plugins (this work was just started the other day) so its *very* crude at the moment. > I thought about a crude hack: "Syncing" AD attributes to the StatusNet > DB in onCheckPassword. But that would be... well, just a dirty > workaround. Would it be possible to write a plugin redirecting some > queries about user attributes to LDAP? I'm pondering where to add a hook to do this kind of updating. I can assure you in won't be a hack in CheckPassword :-) Authn/authz plugins are very much in flux right now. I'm hoping we can have decent LDAP support at least in 0.9.x, and we'll also possibly have some other system integrated too. If you'd like to help, please join us on Freenode at #statusnet, or just keep writing to this list. Thanks, ~Craig _______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
