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?

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.

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?

cu

   Mario

-- 
The antidote to distasteful or hateful speech is not censorship, but
more speech.

_______________________________________________
StatusNet-dev mailing list
[email protected]
http://lists.status.net/mailman/listinfo/statusnet-dev

Reply via email to