3 ms·

The thing that always killed it for me was the utterly bizarre arbitrary federated login requirement in an otherwise self hosted system. It meant it was impossi

by api 7y ago

The thing that always killed it for me was the utterly bizarre arbitrary federated login requirement in an otherwise self hosted system. It meant it was impossible to use on an intranet, not to mention defeating the self hosted purpose.

detaro 7y ago
But it had e-mail based login?
- zenhack 7y ago
  In fairness, this did come a bit later; it was there for quite a while before the company shut down, but when I first showed up I had a similar wtf reaction since at the time it was just GitHub and Google. But yeah, that was fixed a very long time ago.
zenhack 7y ago
It's possible to log in with just an email address; you don't need to use GitHub or Google. There's an FAQ entry about this too: https://docs.sandstorm.io/en/latest/administering/faq/#why-do-you-support-only-google-github-and-passwordless-email-for-login https://docs.sandstorm.io/en/latest/administering/faq/#why-d... Though that doesn't address the intranet issue of course.
mkj 7y ago
The enterprise features for SAML and LDAP authentication are now open source too. https://docs.sandstorm.io/en/latest/administering/for-work/#authentication-provider-ldap https://docs.sandstorm.io/en/latest/administering/for-work/#...
ocdtrekkie 7y ago
Besides avoiding having to manage its own authentication system, one important future direction is federation. So ensuring you can associate accounts as being ‘the same person’ on multiple servers is a significant boon for the future. As a community, many of our conversations and notes are spread across five or six servers in different people’s control. We’d like a better experience for that long term. Email login is pretty good now though if you don’t want to deal with Google or GitHub, and now that LDAP and SAML is available for free, intranet is pretty doable with standard conventions known to most IT departments.
- mathnmusic 7y ago
  Cloudron.io's approach seems far more easier for developers to adopt. Every webapp runs in a Docker container and auth/user management is delegated to a single-sign-on service. But it's not open-source. Sandstorm explains why they don't use Docker: https://sandstorm.io/news/2014-08-19-why-not-run-docker-apps https://sandstorm.io/news/2014-08-19-why-not-run-docker-apps But the problem with the ease of adoption remains.
  - ocdtrekkie 7y ago
    Cloudron is definitely easier to build and integrate apps for than Sandstorm. And it is open source now, although automatic updates require a license. However, Sandstorm’s security model is a step beyone what something Docker based can offer.
    - polyglotnetwork 7y ago
      > And it is open source now I don't think so. Here's their license: https://git.cloudron.io/cloudron/box/blob/master/LICENSE https://git.cloudron.io/cloudron/box/blob/master/LICENSE
      - ocdtrekkie 7y ago
        Oh, that’s unfortunate. It looks like they replaced the AGPL with that 11 months ago. It used to be open source!
deleted 7y ago
[deleted]

by api 7y ago

detaro 7y ago

But it had e-mail based login?

zenhack 7y ago
In fairness, this did come a bit later; it was there for quite a while before the company shut down, but when I first showed up I had a similar wtf reaction since at the time it was just GitHub and Google. But yeah, that was fixed a very long time ago.

zenhack 7y ago

It's possible to log in with just an email address; you don't need to use GitHub or Google. There's an FAQ entry about this too: https://docs.sandstorm.io/en/latest/administering/faq/#why-do-you-support-only-google-github-and-passwordless-email-for-login https://docs.sandstorm.io/en/latest/administering/faq/#why-d... Though that doesn't address the intranet issue of course.

mkj 7y ago

The enterprise features for SAML and LDAP authentication are now open source too. https://docs.sandstorm.io/en/latest/administering/for-work/#authentication-provider-ldap https://docs.sandstorm.io/en/latest/administering/for-work/#...

ocdtrekkie 7y ago

Besides avoiding having to manage its own authentication system, one important future direction is federation. So ensuring you can associate accounts as being ‘the same person’ on multiple servers is a significant boon for the future. As a community, many of our conversations and notes are spread across five or six servers in different people’s control. We’d like a better experience for that long term. Email login is pretty good now though if you don’t want to deal with Google or GitHub, and now that LDAP and SAML is available for free, intranet is pretty doable with standard conventions known to most IT departments.

mathnmusic 7y ago
Cloudron.io's approach seems far more easier for developers to adopt. Every webapp runs in a Docker container and auth/user management is delegated to a single-sign-on service. But it's not open-source. Sandstorm explains why they don't use Docker: https://sandstorm.io/news/2014-08-19-why-not-run-docker-apps https://sandstorm.io/news/2014-08-19-why-not-run-docker-apps But the problem with the ease of adoption remains.
- ocdtrekkie 7y ago
  Cloudron is definitely easier to build and integrate apps for than Sandstorm. And it is open source now, although automatic updates require a license. However, Sandstorm’s security model is a step beyone what something Docker based can offer.
  - polyglotnetwork 7y ago
    > And it is open source now I don't think so. Here's their license: https://git.cloudron.io/cloudron/box/blob/master/LICENSE https://git.cloudron.io/cloudron/box/blob/master/LICENSE
    - ocdtrekkie 7y ago
      Oh, that’s unfortunate. It looks like they replaced the AGPL with that 11 months ago. It used to be open source!

deleted 7y ago

[deleted]