Support for SSO/OIDC #196
Replies: 3 comments
|
Hey @hanneshier Thanks for the suggestion! I agree—while it might not make sense for the cloud version (app.trypost.it), it would definitely be a great addition for self-hosted instances like your NGO's. Like many other features in Trypost, we can use ENV variables to toggle it, so I can simply disable it for the cloud side. If you're open to working on a PR for this, you are more than welcome to do so! My only request is to ensure it isn't hardcoded specifically to Authentik. It would be best to use a standard SSO protocol (like OpenID Connect or OAuth2) so it can support other providers as well. This way, self-hosters can just set their environment variables and have it work out of the box. Sounds good? |
|
Unfortunately, I don't have the necessary coding experience to implement that. I don't think a security-related feature like authentication should be vibe-coded by me without understanding it. However, I'd be more than happy to help with testing or writing documentation if someone finds the time to implement it! I also agree that I should definitely use a standard such as OpenID Connect. I think OIDC is most commonly used for self-hosted apps, so I would prefer it to something like SAML. And btw, thank you for open-sourcing this software! It's much appreciated, especially by our small NGO, which doesn't have the funds to pay for lots of subscriptions ❤️ |
|
Hi, @hanneshier! Don't worry! I'll add this to our development backlog; I think it makes sense. Also, thanks a lot for the feedback, man 👊 |
Uh oh!
There was an error while loading. Please reload this page.
It would be great to have the option to use custom SSO endpoints, rather than being limited to Google or GitHub. For instance, we use Authentik in our small, volunteer-run NGO, which allows us to log in to all our services with a single password. I’m not sure how that would apply to the hosted version, but it would certainly be a great addition to the self-hosted version.
All reactions