Authelia OIDC redirect to c10y does not work with pre-established authelia session #2069
Labels
No labels
Abandoned
Blocked
Bug
Changelog
Added
Changelog
Missing
Changelog
None
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Merge
Merge/Manual
Merge/Squash
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
bob the builder
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity#2069
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi, I'm facing a weird issue with authelia OIDC. I set up OIDC in c10y with
and the following authelia config
which works perfectly when starting the sign in flow with a fresh authelia session:
On the log in screen, the
Continuebutton takes me tohttps://auth.example.at/?flow=openid_connect&flow_id=cedce9f6-4b1d-4fe3-ab7b-1e8e964a541f(my authelia instance), I provide my authelia credentials, consent to OIDC, and get redirected to c10y. After this the (code to token?) exchange happens between c10y and authelia and I am signed into matrix.However, if I already have an authenticated authelia session established and try to do the sign in flow,
I never get redirected back to c10y, the browser simply stays on the authelia page.
The browser developer tools show a GET request:
https://auth.example.at/api/oidc/authorization?response_type=code&client_id=c10y&state=axqYvGexzhjFOE83rYzVeQ&code_challenge=cNRn96Vc4drLKN0BNq1piK5KA4S_xBYbgdn-X8Yl3Ug&code_challenge_method=S256&redirect_uri=https%3A%2F%2Fmatrix.example.de%2F_continuwuity%2Foidc%2Fcomplete&scope=openid+profile+email&nonce=IU2JyAqrf7_cpxpbixLFXQand then a redirect to
https://auth.example.at/?flow=openid_connect&flow_id=ee703995-ab29-40c1-8ed6-4213a731ec47where the browser gets stuck.The authelia logs only show the authentication but no attempt at any redirect back to c10y is being made
Everything after the first
302response is just authelia loading its UI, I believe.The c10y logs show literally nothing in this second case (which I think is expected since everything before the redirect back to c10y happens between the auth server and the browser, right?)
Can anyone think of a reason for this behaviour? My first instinct would be that i misconfigured authelia, but all my other (numerous) OIDC clients work without issue.
Thanks in advance!
continuwuity 26.7.1 (
83cf15b)authelia version v4.39.20
Tested in Firefox and Chromium
Thanks for the thorough report. This seems very likely to be an issue with Authelia, not continuwuity, since other OIDC-compatible IDPs are known to work correctly, but if you're able to narrow this down to a behavior of continuwuity specifically please amend this issue with more detail and we'll take another look.