Repository navigation
Authelia says Karakeep is buggy and not OIDC compliant. Is this still true? #3119
Replies: 3 comments 3 replies
|
In case this helps: having recently evaluated Authelia as an OIDC provider, I was put off by the complexity of its setup and eventually landed on Pocket ID as my preferred OIDC provider that is not only simple to set up and maintain, but looks better too, although it offers fewer features than Authelia provides. Today in my Karakeep v0.33.2 I've set up OIDC login with Pocket ID as a provider, and it worked first try without a hitch. Based on this experience, I would say that Karakeep's OIDC implementation is not buggy (at least when it comes to basic functionality). # Karakeep env config
OAUTH_SCOPE="openid email profile"
OAUTH_ALLOW_DANGEROUS_EMAIL_ACCOUNT_LINKING="true"
OAUTH_TIMEOUT="3500"
OAUTH_PROVIDER_NAME="Pocket ID"
OAUTH_CLIENT_ID=******
OAUTH_CLIENT_SECRET=******
OAUTH_WELLKNOWN_URL="https://{POCKETID_URL}/.well-known/openid-configuration" |
|
I also want to say that I've just landed a major migration from out oauth library last weekend. So the nightly build now runs a completely different oidc implementation using a very popular and modern library (better-auth) compared to what we've been using before (next-auth). Hopefully this should eliminate whatever problems left in the oidc implementation we have. |
Uh oh!
There was an error while loading. Please reload this page.
The configuration page for Karakeep on Authelia's official documentation website claims that Karakeep's OpenID Connect 1.0 implementation has significant bugs which make it non-compliant and making it work properly with Authelia requires a workaround.
However, the version these claims were made against is over a year old v0.26.0. Are these claims still true? Can someone check and verify and maybe correct the documentation if these hacks are no longer necessary?
All reactions