Replies: 2 comments 2 replies
-
There isn't any documentation or prior discussion about setting up OIDC with Authelia for Blinko. The error you're seeing happens because Blinko expects the OIDC userinfo response to include a sub (subject) claim, which is required by the OIDC spec and mapped to profile.id in Blinko's code. If Authelia's /userinfo endpoint doesn't return sub, or it's null/undefined, Blinko will throw this error when it tries to call .toString() on it. Make sure your Authelia configuration and userinfo endpoint return a valid sub claim in the response for Blinko to work correctly with OIDC. You can see this expectation in the Blinko code handling custom OAuth providers and user profile mapping [source]. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
-
The solution was to use the well-known endpoint |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I want to set up IODC with Authelia. It worked in the past, and now that I am completely moving to Blinko from scratch I cannot reproduce the SSO setup 😒 I get an error that does not say much about the underlying cause.
Has anyone documented their setup with Authelia?
Right now with the Authelia setup
I get the error in Blinko after the Authelia consent page:
The Blinko configuration is:
Beta Was this translation helpful? Give feedback.
All reactions