github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[Feature] Allow self-signed certificates for OpenID (Self-Hosted/Development SSO Environment) #2315

New Issue
Closed
opened 2026-02-28 20:10:14 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 20:10:14 -06:00
Owner
Copy Link

Originally created by @Kryszn0 on GitHub (Jul 27, 2025).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

My self-hosted SSO/OpenID provider utilizes a self-signed certificate, which my server trusts but docker containers usually do not.

When trying to link Actual Budget to my SSO via OpenID I receive the following error:

Error setting up OpenID client: Error: self-signed certificate at TLSSocket.onConnectSecure (node:_tls_wrap:1677:34) at TLSSocket.emit (node:events:524:28) at TLSSocket._finishInit (node:_tls_wrap:1076:8) at ssl.onhandshakedone (node:_tls_wrap:862:12) { code: 'DEPTH_ZERO_SELF_SIGNED_CERT' }

Since this is for my personal finances and I am building my homelab to be entirely "offline" I don't want to utilize certificates from external authorities (e.g., LetsEncrypt).

Would it be possible to enable this "insecure" certificate via an environment variable option?

Describe your ideal solution to this problem

I believe the solution for what I'm describing is here. But I'm not sure how exactly to implement this in my docker container.

Again, this is really only necessary for development/self-hosted environments and I believe it would really only affect OpenID and not much else?

Teaching and learning

No response

Originally created by @Kryszn0 on GitHub (Jul 27, 2025). ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? My self-hosted SSO/OpenID provider utilizes a self-signed certificate, which my server trusts but docker containers usually do not. When trying to link Actual Budget to my SSO via OpenID I receive the following error: `Error setting up OpenID client: Error: self-signed certificate at TLSSocket.onConnectSecure (node:_tls_wrap:1677:34) at TLSSocket.emit (node:events:524:28) at TLSSocket._finishInit (node:_tls_wrap:1076:8) at ssl.onhandshakedone (node:_tls_wrap:862:12) { code: 'DEPTH_ZERO_SELF_SIGNED_CERT' }` Since this is for my personal finances and I am building my homelab to be entirely "offline" I don't want to utilize certificates from external authorities (e.g., LetsEncrypt). Would it be possible to enable this "insecure" certificate via an environment variable option? ### Describe your ideal solution to this problem I believe the solution for what I'm describing is [here](https://github.com/request/request/issues/418). But I'm not sure how exactly to implement this in my docker container. Again, this is really only necessary for development/self-hosted environments and I believe it would really only affect OpenID and not much else? ### Teaching and learning _No response_
GiteaMirror added the featureneeds votes labels 2026-02-28 20:10:14 -06:00
GiteaMirror commented 2026-02-28 20:10:16 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 27, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Jul 27, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2315
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?