Open Firstyear opened 1 year ago
welcome[bot]
commented
1 year ago 👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
phil-flip
commented
8 months ago Technically, Google OAuth is already OIDC, is it not?
Firstyear
commented
8 months ago Technically, Google OAuth is already OIDC, is it not?
Google Oauth is an OIDC authentication provider. This is a request that Snipe supports being a relying party who consumes OIDC from an authentication provider such as google.
olivierlambert
commented
8 months ago +1 on this, that would be wonderful to get SnipeIT login via an SSO portal in OIDC (like Keycloak). OIDC is pretty simple to configure as an admin :) (unlike SAML and such)
Blackclaws
commented
5 months ago I have to add that its not just simpler to setup its also much less prone to misconfiguration as the relying party can pull the configuration from the attesting party. Definitely +1 on this request.
mustard123
commented
1 week ago +1 on this, that would be wonderful to get SnipeIT login via an SSO portal in OIDC (like Keycloak). OIDC is pretty simple to configure as an admin :) (unlike SAML and such)
Keycloak would be amazing and is absolutely needed
Is your feature request related to a problem? Please describe.
OpenID Connect is a popular alternative to SAML that has been growing in adoption an used. It is an extension of Oauth2 allowing structured user information to be provided to the relying party.
Extending Snipe-IT to support OIDC would allow integration with a broader range of authentication providers.
OIDC is defined https://openid.net/specs/openid-connect-core-1_0.html
Describe the solution you'd like
Snipe IT to allow OIDC as a parallel alternative to SAML.
Describe alternatives you've considered
n/a
Additional context
No response