[GH-ISSUE #4907] [Bug]: Unable to configure OpenID (Authelia) #51206

Closed
opened 2026-04-30 17:08:06 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @yash-garg on GitHub (May 1, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4907

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

We've removed the enable-openid script in https://github.com/actualbudget/actual/pull/4428, I have all the necessary environment variables set for this to work:

  • ACTUAL_ALLOWED_LOGIN_METHODS: openid
  • ACTUAL_LOGIN_METHOD: openid
  • ACTUAL_OPENID_ENFORCE: true
  • ACTUAL_OPENID_DISCOVERY_URL: https://auth.tld
  • ACTUAL_OPENID_CLIENT_ID: <client_id>
  • ACTUAL_OPENID_CLIENT_SECRET: <client_secret>
  • ACTUAL_OPENID_SERVER_HOSTNAME: https://budget.tld
  • ACTUAL_OPENID_AUTH_METHOD: oauth2

It still showed me a password screen for login instead of OpenID. I had to manually add the enable-openid script to package.json and use npm run enable-openid to get the desired behavior.

Client Version: v25.4.0
Server Version: v25.4.0

Is this expected?

Where are you hosting Actual?

Home Server

What browsers are you seeing the problem on?

All

Operating System

unRAID

Originally created by @yash-garg on GitHub (May 1, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4907 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? We've removed the `enable-openid` script in https://github.com/actualbudget/actual/pull/4428, I have all the necessary environment variables set for this to work: - `ACTUAL_ALLOWED_LOGIN_METHODS`: `openid` - `ACTUAL_LOGIN_METHOD`: `openid` - `ACTUAL_OPENID_ENFORCE`: `true` - `ACTUAL_OPENID_DISCOVERY_URL`: `https://auth.tld` - `ACTUAL_OPENID_CLIENT_ID`: `<client_id>` - `ACTUAL_OPENID_CLIENT_SECRET`: `<client_secret>` - `ACTUAL_OPENID_SERVER_HOSTNAME`: `https://budget.tld` - `ACTUAL_OPENID_AUTH_METHOD`: `oauth2` It still showed me a password screen for login instead of **OpenID**. I had to manually add the `enable-openid` script to `package.json` and use `npm run enable-openid` to get the desired behavior. Client Version: `v25.4.0` Server Version: `v25.4.0` Is this expected? ### Where are you hosting Actual? Home Server ### What browsers are you seeing the problem on? All ### Operating System [unRAID](https://unraid.net/)
GiteaMirror added the bug label 2026-04-30 17:08:06 -05:00
Author
Owner

@lelemm commented on GitHub (May 1, 2025):

This will be fixed with this PR #4902

<!-- gh-comment-id:2844846618 --> @lelemm commented on GitHub (May 1, 2025): This will be fixed with this PR #4902
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#51206