5 ms·
Surprised to see no LDAP support. http://www.fossil-scm.org/index.html/tktview?name=ec667f74f8 http://www.fossil-scm.org/index.html/tktview?name=ec667f74f8
by simplehuman 10y ago
Surprised to see no LDAP support.
http://www.fossil-scm.org/index.html/tktview?name=ec667f74f8 http://www.fossil-scm.org/index.html/tktview?name=ec667f74f8
- djsumdog 10y agoFrom what I can tell from the issue, they're suggesting the load balancer or server you put in front of Fossil to do the authentication (which can hit LDAP/AD). Sure you can't do fine grained control or permissions, but for small shops/groups it seems like a good starting point.
- lvh 10y agoYou can sort-of hack it together offline, in that LDAP can be the source of identity (via REMOTE_USER + frontend, as you mention), and that Fossil has a reasonably fine-grained permissions model that you can (offline) sync from LDAP.
- tokenizerrr 10y ago> Sure you can't do fine grained control or permissions, but for small shops/groups it seems like a good starting point. That seems like a terrible compromise.
- rkeene2 10y agoFossil can work over HTTP or SSH. Over HTTP you can authenticate using any method your web server supports, or the built-in Fossil authentication. For SSH, you can authenticate using any method your SSH server supports.