[BUG] auth doesnt work, especially keycloak

[Ev0genii]

Environment

Self-Hosted (Docker)

System

debian

Version

2.1.1

Describe the problem

Deploy dashy in kubernetes with ingress
tried to make auth by dashy documentation, but it didnt work, even basic auth with user hash and title
also auth parameters as enableGuestAccess doesnt work
i think its something in last update, that interfere auth work
last git update was a week ago, maybe u didnt update documentation

Additional info

No response

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}

[juancarlosm]

Same here. Basic auth is not working.

[randyjc]

Was about to give up, because I couldn't find what I was doing wrong.
Tried a couple of different options, but below is latest.
After applying below to the config, I also get the message that I'm not logged in as admin.
When trying to force via URL to login I just get redirected to Dashy homepage.

https://url/login redirects to https://url/

I deleted cache, restarts, incognito, other browsers etc.

appConfig:
  theme: nord-frost
  layout: auto
  iconSize: medium
  language: en
  auth:
    users:
    - user: randyjc
      hash: <REDACTED>
      type: admin
pageInfo:
  title: Dashy
  description: Welcome to your new dashboard!
  navLinks:
    - title: GitHub
      path: https://github.com/Lissy93/dashy
    - title: Documentation
      path: https://dashy.to/docs
sections:
  - name: Getting Started
    icon: fas fa-rocket
    items:
      - title: Dashy Live
        description: Development a project management links for Dashy
        icon: https://i.ibb.co/qWWpD0v/astro-dab-128.png
        url: https://live.dashy.to/
        target: newtab
        id: 0_1481_dashylive
      - title: GitHub
        description: Source Code, Issues and Pull Requests
        url: https://github.com/lissy93/dashy
        icon: favicon
        id: 1_1481_github

V2.1.1 via PikaPods

EDIT: Probably related: #1126

[artemdanielov]

same here, auth (basic) doesnt work =(

[ajbrigg49]

I am new to Dashy (Just set it up about a week ago.) Today I was following the basic auth docs and I am also seeing the same issue. Opening Dashy, I just get to my dashboard. If I go to config, update config, edit config, I see a message across the bottom "You cannot write changes to disk because you are not logged in as an administrator". So it would seem it knows about my new user account that is an admin, however it is not redirecting to login. I've tried multiple browsers (Edge, chromium, Chrome), and multiple PCs, but there is no change. If it matters, I added the auth config by hand from ssh use VI.

Thanks

Andy

[clockwinder]

I seem to be having a similar issue.

[chrgraham]

+1 Basic auth is NOT working, new user running Docker, auth is configured, dashboard is completely exposed and unsecured.

Have attempted these additional configuration options mentioned in other Issues.

    enableGuestAccess: false
    disableConfigurationForNonAdmin: true

Here is my entire appConfig:

appConfig:
  theme: nord-frost
  layout: auto
  iconSize: medium
  language: en
  auth:
    enableGuestAccess: false
    disableConfigurationForNonAdmin: true
    users:
    - user: *****
      hash: *****
      type: admin

Auth tickets should be a priority.

Related to these other Issues that are getting closed from the timeout bot. It does not appear the repo owner @Lissy93 is responding these.

• [BUG] Authentication does not work correctly #1082
• [BUG] Basic Auth not Working #1063
• [BUG] basic auth does not enable unless enableGuestAccess: true #990
• [BUG] redirect keycloak stopped working #1019

[Pytonballoon810]

Is this still going on? I think I have the same problem but cant seem to find a fix if there is maybe someone can direct me into the right direction?

[clockwinder]

I've not found a solution yet. So for now I've just disabled Dashy.

[IbaiBuR]

I am experiencing the same issue too... Neither keycloak nor basic auth working...

Lets hope @Lissy93 can fix it soon somehow.

[bloodysneaker]

+1
No login page showing after enabling auth.
With the aforementioned work-around of "enableguestaccess" I've the login button but even if I authenticate with an Admin user, I'm no able to make any conf changes.

EDIT: Reverting to 2.1.0 seems to fix the issue

[Maretzky85]

+1 on docker swarm
2.1.0 docker image works fine tho.
Keeping previous version until fix is available :)

Btw. Thanks for superb app, and no pressure ;)

[pikmin-rgb]

Hello @CrazyWolf13 !

I am still having issue with dashy blocked in a never ending refresh. I have the page with auth with keycloak, and when I am login in, I have dashy that is stuck refreshing and not working.

I don't know if its still an issue with dashy or if it is a config problem :(

[CrazyWolf13]

@Unacoli
Thanks for the feedback, can you confirm you are indeed running the latest version of dashy and can you try to repull and redeploy the container?

Also would you mind sharing your conf.yml ?

[zell-mbc]

I have a sort of working setup in case you want to compare notes.
"Sort of" because when I do a docker compose down --rmi all && docker compose up -d I have to do a separate rebuild via docker exec -it dashboard yarn build

Without the later docker command Dashy will work, but not ask for credentials, which is the opposite of fail-safe I guess :-)

[CrazyWolf13]

Thanks for sharing, also is that still happening in 2.1.2 ? Because in the new version dashy should rebuild at start?

[zell-mbc]

Yes, this is what I am running:

dashboard | Using Dashy V-2.1.2. Update Check Complete

[pikmin-rgb]

Yes I am indeed running the latest version.

pageInfo:
  title: Hub
sections:
  - name: Example Section
appConfig:
  theme: callisto
  language: fr
  layout: auto
  iconSize: medium
  startingView: default
  defaultOpeningMethod: newtab
  statusCheck: false
  statusCheckInterval: 0
  faviconApi: allesedv
  routingMode: history
  enableMultiTasking: false
  widgetsAlwaysUseProxy: false
  webSearch:
    disableWebSearch: false
    searchEngine: duckduckgo
    openingMethod: newtab
    searchBangs: {}
  enableFontAwesome: true
  enableMaterialDesignIcons: false
  hideComponents:
    hideHeading: false
    hideNav: false
    hideSearch: false
    hideSettings: false
    hideFooter: false
  auth:
    enableGuestAccess: false
    users: []
    enableKeycloak: true
    keycloak:
      serverUrl: [URL]
      realm: [Realm]
      clientId: [id]
      legacySupport: false
      idpHint: [idp]
  showSplashScreen: false
  preventWriteToDisk: false
  preventLocalSave: false
  disableConfiguration: false
  disableConfigurationForNonAdmin: false
  allowConfigEdit: true
  enableServiceWorker: false
  disableContextMenu: false
  disableUpdateChecks: false
  disableSmartSort: false
  enableErrorReporting: false

[pikmin-rgb]

I have a sort of working setup in case you want to compare notes. "Sort of" because when I do a docker compose down --rmi all && docker compose up -d I have to do a separate rebuild via docker exec -it dashboard yarn build

Without the later docker command Dashy will work, but not ask for credentials, which is the opposite of fail-safe I guess :-)

The command sadly didn't solved the refresh problem :( I really don't understand if the problem come from me or not since its gave me the right connexion prompt, and after login its locked in the refreshing state (i also see my connexion log on dashy on the keycloak log)

[pikmin-rgb]

I've investigated a little more browsing tickets, and I find the answer to my problem !

In Keycloak, in my dashy client, I had to turn off this option :

It works perfectly now, thank you all !

And for note, the command docker exec -it dashboard yarn build provided by @zell-mbc is usefull , the login screen don't show up without it after a docker compose up -d

Edit :

I've added the line entrypoint: ["yarn","build-and-start"] in my docker-compose.yml, it replaces the command docker exec -it dashboard yarn build :)

[e-sacchi]

I also have this problem, normal login works, keycloak not, even with this feature disabled... No login page and config file open to anyone. Any updates on this?

[Kirkland-gh]

Keycloak is working for me now on 3.0.0 when I go to dashy.domain.com/login. Is anyone else able to test?

[kutekroma]

Console output after keycloak authorization:

Error while trying to use the following icon from the Manifest: https://***.domen.com/web-icons/dashy-pwa_144x144.png (Download error or resource isn't a valid image)

Warning : Deprecation warning: The simple-icons entrypoint will be removed in the next major. Please switch to using import * as icons from "simple-icons/icons" if you need an object with all the icons.

[kutekroma]

Keycloak is working for me now on 3.0.0 when I go to dashy.domain.com/login. Is anyone else able to test?

can you show conf.yml and a screenshot of the clients setting in keycloak?
Have you set up roles and groups separately in the client?

[Kirkland-gh]

Keycloak is working for me now on 3.0.0 when I go to dashy.domain.com/login. Is anyone else able to test?

can you show conf.yml and a screenshot of the clients setting in keycloak? Have you set up roles and groups separately in the client?

Only one user so no roles or groups.

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

[Lissy93]

I hadn't realized that the infinite refresh loop was client-side, sorry misunderstood and thought you were talking about a Docker issue.

This should be fixed by db9d7e3 in #1542 and released in 3.0.1

[kutekroma]

Great! It works with version 3.0.1
THANKS!!!!!