OpenID Connect (OIDC) for Sync-in

[Nonoss117]

Hi,

my Christmas letter, implementation of OpenID Connect (OIDC) for Sync-in

I acces to Sync-in through a SSO app with Pangolin
I'm going to add an OIDC provider (Authelia, or something else, I didn't choose yet) to access to my containers, and of course Syn-in

Thank's 😀

[Cherryblue]

Agreed, while having LDAP is very good, as far as external auth is a thing, the difficulty is having multiples services where some are ldap-only (which is currently the case of sync-in to my understanding) and some are oidc-only.

would be great to have oidc/sso too :).

[johaven]

my Christmas letter, implementation of OpenID Connect (OIDC) for Sync-in

Seems like Santa got delayed on the way 🎅
But the OIDC implementation for Sync-in has finally arrived!

[Nonoss117]

Hello @johaven thank you very much for this implementation and for all your work on Sync-in

[boobin]

Hello,

Thx a lot for all this work ! I was trying to use a google oauth token but had no success so far (401 from google "The OAuth client was not found"). Problem is most probably on my side, but i couldn't find it.

Just curious if this IDP had been tested with sync-in, and if anyone noticed any pitfall with the client id creation and/or syncin oidc config.

[johaven]

@boobin Google is definitely not a religion here 🙂, but it should work out of the box with Sync-in; the most common pitfall is forgetting to properly declare the Authorized redirect URI in the Google OAuth configuration: https://sync-in.domain.com/api/auth/oidc/callback. The Client ID must be declared both in the Google OAuth configuration and in the Sync-in configuration.