<xet7>
sy: LDAP and SAML users, passwords are defined at LDAP/SAML servers. I presume Sandstorm does not affect those in any way.
<xet7>
sy: I presume 2fa depends on your LDAP/SAMP/other auth server. Not Sandstorm.
<xet7>
sy: because that auth server takes care of all auth steps, like 2fa etc.
<xet7>
sy: About groups, you need to test do they work with Sandstorm.
<xet7>
sy: I presume all this, because both Sandstorm and Wekan are made with Meteor, and also Standalone Wekan can not affect any LDAP settings.
<xet7>
sy: I would think that adding more login/permission etc features to Sandstorm would take a lot of work. Someone can anyway try implement more stuff and add pull request.
<xet7>
sy: I think that way, because I still have not figured out all Sandstorm permission stuff while maintaining Wekan and keeping it running on Sandstorm, I have still many Sandstorm specific Wekan bugs to fix.
<sy>
alright cool, thanks
<sy>
not sure ldap can do 2fa though
<sy>
saml will redirect you to a page, but ldap just takes arguments
<sy>
i suppose it can take 3 arguments, one for the TOTP
<sy>
but sandstorm would need to know about this to present it
<xet7>
In general, Sandstorm only stores generated random user ID, not any password data.
<xet7>
That is part of security design of Sandstorm.
<xet7>
Ooops I released experimental broken version of Wekan. Just a moment I fix it.
<xet7>
experimental broken Sandstorm version
<xet7>
It's so fun. Upgrade some dependency, then Wekan breaks, so downgrading dependency :D