User journey

[bjarneo]

• Super admin
• • Configuration panel for the self hosted version (logo, colors)
• • This includes allowed accounts / i.e. based on email. Block sign in and more ([BUG] Disable user registration also disable login for previously registered users #94)
• Diffie-Hellman (Diffie-Hellman for the encryption #69)
• Organizations
• "Friends" (so you can easily use the DH algorithm)

[luismanson]

Hello, I saw issue #94 a few days ago and saw you the "user journey" but im not familiar with that concept. Would you consider to allow logins regardless of registration being disabled or add another setting to control this?

[d-513]

probably would be best to have an option to create an admin account with env variables, and disable upload for non admins. I don't want random people uploading shit to my server.
Also, LDAP support would be quite useful for me, is that desired? If so, I can get a quick PR going for it

[bjarneo]

@luismanson / @dada513

Yeah, it would be an admin dashboard where you can adjust the settings you would like for your application. That is my thoughts on this as well.

So the admin allows either anyone to register an account. Organizations. Add people manually. Or something in between here.

@dada513 Sure, feel free to create LDAP support. I think more people would have the need of that as well

[d-513]

@bjarneo I think for settings it's alright to do it like other services and just have configuration via environment variables, like HEMMLIG_ALLOW_REGISTER, makes deployment easier to be automated. But an admin panel would be useful for creating users though

[Zulgrib]

Where would these settings be stored? Plain files? Database? Would it automatically alter default.cjs or production.cjs? Add an additional file?

Using env variables bloats the systemd service file and may allow unix users on host to view the variable content where a configuration file or store in database is easier to restrict.

[bjarneo]

It will be saved to the database whenever that part is ready.

[bjarneo]

The database switch using sqlite has now been implemented, much thanks to @d-513. 560831d

From version 5.0.0 it makes it easier to implement features such as this. Here is a list of tickets that will now be possible:

#94
#26
#168
#24

[bjarneo]

#154