[BUG] redirect keycloak stopped working

[wolflarson]

Environment

Self-Hosted (Docker)

System

Firefox 108.0.1 (64-bit) on Manjaro (KDE)

Version

2.1.1

Describe the problem

While on 2.1.1 redirect to keycloak is not forced. Downgrading to 2.1.0 correctly forces login via keycloak before showing dashboard.

This is the auth block. My config is not changing between versions. Upgrade to 2.1.1 and no login needed. Downgraded and I'm forced to login via keycloak before I can interact. This might actually be a security issue because on 2.1.1 I can edit the config yaml without logging in.

  auth:
    enableGuestAccess: false
    users: []
    enableKeycloak: true
    keycloak:
      serverUrl: https://auth.example.com
      realm: example
      clientId: dashy
      legacySupport: false

I reset the config file to stock and only changed this auth block to replicate the issue before opening a bug. Full config can be found here.

Additional info

keycloak:20.0.2

Please tick the boxes

• You have explained the issue clearly, and included all relevant info
• You are using a supported version of Dashy
• You've checked that this issue hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

[liss-bot]

If you're enjoying Dashy, consider dropping us a ⭐
_{🤖 I'm a bot, and this message was automated}

[allesauseinerhand]

Probably the same source of bug for this problem: #990

[ouafnico]

I actually got the same bug on 2.1.1.
I have to use 2.1.0 too.

On 2.1.1, the "disconnect" button is present, but does nothing, and I can't go to the login page.

Thanks btw for dashy, it's very good !

[djessich]

I switched back to 2.1.0. Version 2.1.1 stopped working for me too.
After some time, Dashy does not redirect anymore, so redirection is not forced.

[kieraneglin]

This may have been fixed by #1026 but I have not confirmed

[wolflarson]

Should the 2.1.1 docker container include that change at this point? I can test quickly if there is a container built already .

[ouafnico]

I'm using the 2.1.1 but I still got a bug : guest access is not working, and got a continuous refresh of page.

[liss-bot]

This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.

[liss-bot]

This issue was automatically closed because it has been stalled for over 6 weeks with no activity.

[zell-mbc]

This one shows as closed, but it isn't for me. I was running v2.1.1 until today when I realised that my dashboard has been unprotected since December.
I would actually think this should be treated like a pretty serious/security related regression?

A downgrade to v.2.0.0 as recommended higher up, made things working again.

[TheRealGramdalf]

See #1290 (comment) for a full explanation/semi solution

For notifications:
@jakob1379 @zell-mbc @ouafnico @wolflarson @kieraneglin @djessich @allesauseinerhand
Sorry if you didn't want to be pinged, but I figure you probably did - or you wouldn't have participated in the issue

[jakob1379]

See #1290 (comment) for a full explanation/semi solution

For notifications:
@jakob1379 @zell-mbc @ouafnico @wolflarson @kieraneglin @djessich @allesauseinerhand
Sorry if you didn't want to be pinged, but I figure you probably did - or you wouldn't have participated in the issue

My isse was a misconfiguration with keycloak.