You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 14, 2022. It is now read-only.
Most organisations (or associations) use LDAP for user management. It is the case for my own infrastructure.
I would like to provide a hashbase instance for my users, but for that it needs to integrate into the "single account" policy.
Adding LDAP support might be a little tricky as user names can have special characters like @. For instance, on my infrastructure the username is always the email adress on the form firstname@lastname.fr.
Therefore either username allow dots and "@", or better the user should be able to log either with his username or with his email adress. When a user connects for the first time with his email then he is asked to choose a username.
See the following thread for Mastodon support of LDAP:
tootsuite/mastodon#7857
tootsuite/mastodon#6830
As long as hashbase doesn't support LDAP (OpenLDAP), it will be difficult to make a proper package for self-hosting "cloud" distribution like Yunohost or Freedombox...
The strength of hashbase is to contribute to (re)decentralize the usage of Internet and thus share this will with self-hosting server distribution.
To optimize this strength, I believe hashbase should spread as much as possible on servers and so be easy to install and fit into these distributions. LDAP is a feature that really make it easy to manage a software on this kind of distribution and make it user friendly for those who are simple user of family or neighbourly, local cloud.
Most organisations (or associations) use LDAP for user management. It is the case for my own infrastructure.
I would like to provide a hashbase instance for my users, but for that it needs to integrate into the "single account" policy.
Adding LDAP support might be a little tricky as user names can have special characters like @. For instance, on my infrastructure the username is always the email adress on the form firstname@lastname.fr.
Therefore either username allow dots and "@", or better the user should be able to log either with his username or with his email adress. When a user connects for the first time with his email then he is asked to choose a username.
See the following thread for Mastodon support of LDAP:
As long as hashbase doesn't support LDAP (OpenLDAP), it will be difficult to make a proper package for self-hosting "cloud" distribution like Yunohost or Freedombox...
The strength of hashbase is to contribute to (re)decentralize the usage of Internet and thus share this will with self-hosting server distribution.
To optimize this strength, I believe hashbase should spread as much as possible on servers and so be easy to install and fit into these distributions. LDAP is a feature that really make it easy to manage a software on this kind of distribution and make it user friendly for those who are simple user of family or neighbourly, local cloud.
It would be nice to see a yunohost package of hashbase coming.
https://yunohost.org
https://github.com/YunoHost-Apps/
The text was updated successfully, but these errors were encountered: