[BUG] hideForKeycloakUsers does not hide elements

[jakob1379]

Environment

Self-Hosted (Docker)

System

firefox 112, docker version 23.0.4

Version

2.1.1

Describe the problem

I have setup a selfhosted keycloak instance as described in the docs for dashy and (hide|show)ForKeycloakUsers does not seem to work as expected. The login part worked after downgrading from 2.1.1. to 2.1.0 (#678). Now the issue is that my user is part of the group dashyReadOnly as seen here on Keycloak

And in the dashu config I have this

appConfig:
  statusCheckInterval: 0 # service will only be checked on initial page load
  preventWriteToDisk: true
  theme: default
  enableFontAwesome: true
  statusCheck: true
  auth:
    enableGuestAccess: false
    enableKeycloak: true
    keycloak:
      serverUrl: 'https://auth.mypage.com'
      realm: 'test-realm'
      clientId: 'test-client'
      legacySupport: true # remove this if keycloak >= v17

sections: # An array of sections
  - name: Apps
    icon: far fa-rocket
    items:
      - title: test-app
        description: testing the tests to improve other tests
        statusCheckAllowInsecure: true
        icon: si-streamlit
        url: https://tests.com
        displayData:
          hideForKeycloakUsers:
            groups: ['dashyReadOnly']

Now when I log in as the user jga I can still see the item test-app.

Additional info

No response

Please tick the boxes

• [X] You have explained the issue clearly, and included all relevant info
• [X] You are using a supported version of Dashy
• [X] You've checked that this issue hasn't already been raised
• [X] You've checked the docs and troubleshooting guide
• [X] 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}

[itsmejoeeey]

I mentioned on your linked discussion that:

Downgrading to 2.1.0 worked for me, as did the suggested advice to change the entrypoint.

Do you know if the hideForKeycloakUsers issue persists using 2.1.1 with the modified entrypoint?

[jakob1379]

I do not know if the issue is persistent as I am running 2.1.0.

I checked that the token holds the correct group, which it does, so i suspect that something is going wrong in dashy.

[liss-bot]

This issue has gone 3 months 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.

[itsmejoeeey]

This issue is still relevant. I still believe it is related to #1051

[liss-bot]

This issue has gone 3 months 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.

[itsmejoeeey]

Issue is still relevant.

[johnny9798]

@jakob1379 Same issue... any solutions???

[jakob1379]

Just an update - either this has never been a problem OR it has been pushed as a hotfix which does not update the version. See my description here: https://github.com/Lissy93/dashy/issues/1290#issuecomment-1857784047