ChanServ changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things Sandstorm and Cap'n Proto. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev | Channel logs available at https://libera.irclog.whitequark.org/sandstorm
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #sandstorm
xet7 has quit [Remote host closed the connection]
xet7 has joined #sandstorm
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #sandstorm
kentonv has quit [Quit: Leaving]
kentonv has joined #sandstorm
<jfred> Hmm... you know, I wonder if there's a simple OIDC IdP out there that could be run as a Sandstorm app
<jfred> those always feel way overly complex to set up
<ocdtrekkie> Like so a Sandstorm server could serve it's own identity provider as an app?
<ocdtrekkie> That might be a reasonable end run around Sandstorm's default preference not to manage authentication, provided we are offering such an app that we find trustworthy.
<jfred> ah I wasn't even thinking something that involved, just a simple IdP in general for external apps to use - though integrating it with sandstorm's auth might be interesting too
<jfred> mostly just because if you want an OIDC IdP to use with other apps your options are like... one of the proprietary cloud-hosted ones, Keycloak (the setup process for which is a bit intimidating), Gluu (which is maybe a bit less intimidating but still not Sandstorm-easy)... etc
<ocdtrekkie> I just know that since Sandstorm itself supports OIDC, assuming you had at least one admin with email login to set it up, you could probably do something crazy like turn around and use such an app to manage Sandstorm logins too, lol.
<jfred> I'm always afraid of chicken-and-egg problems when you do stuff like that but it *might* be fine :P
<Aziraphale> like making DNS depend on NFS that depends on DNS
<Aziraphale> don't ask me how I know