Hi Oliver; On 12/09/14 5:12 am, Oliver Tappe wrote:
I'm not sure I quite like the idea to make HDS the "source of truth" for user data. I was under the impression that crowd is meant to be exactly that. The problem with maintaing user data in HDS is that it would have to deal with all the Drupal, Trac and ... users. AFAICS, crowd allows to maintain the whole set of users, with using groups/roles to declare access rights.
I don't mind if we use this product. I think it is somewhat important that there is a way that we can extract the user data and password hashes off it in case the project wants to do something different later.
If the Crowd product is employed for user storage, authentication as well as SSO then I should back-out of the changes I am making at the moment for LDAP interfacing because that functionality will not be used.
I don't presently have the time available to investigate / license / deploy / secure / migrate-to etc... the Crowd product. Does anybody else have time to handle this near-term?
cheers. -- Andrew Lindesay