On 09/10/2010 08:00 AM, fossil-users-requ...@lists.fossil-scm.org wrote: > The other alternative is that the storage for usernames is pretty > straightforward for fossil. > Having a 'usersync' tool available for separate download with > out-of-the-box support for pulling in LDAP users > might be an idea better in keeping with fossil philosophy. > I have the http basic authentication working now. It just prompts the user for u/p if the server responds with a 401. That works fine.
The only issue with this setup is that once you have cloned the repository there is no synchronization of username/passwords with our ldap, since when fossil lives on our webserver we aren't really even using the fossil password database. Once the repository is local, fossil uses the internal password database. If the ldap passwords were somehow externally synced as you propose... then after a clone the local passwords would match the ldap ones. This would be cool. James _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
