Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add SSO integration and/or TLS to Uptime Kuma instance #35

Open
2 tasks
lvps opened this issue Nov 6, 2024 · 1 comment
Open
2 tasks

Add SSO integration and/or TLS to Uptime Kuma instance #35

lvps opened this issue Nov 6, 2024 · 1 comment
Labels

Comments

@lvps
Copy link
Member

lvps commented Nov 6, 2024

Both are nearly impossible to achieve, but we can try

  • SSO
  • TLS
@lvps lvps added document it on the wiki Improvements or additions to documentation huge project software configuration labels Nov 6, 2024
@lvps
Copy link
Member Author

lvps commented Nov 6, 2024

SSO seems feasible by disabling authentication completely and placing a (reverse) proxy in front, e.g. https://github.com/oauth2-proxy/oauth2-proxy
Only the Sysadmin group needs access and Keycloak can already provide groups, so it shouldn't be too complicated.

TLS requires port 80 or 443 accessible from the public internet (impossible) or a custom DNS installed somewhere (impossible since the port is probably firewalled) or some "fun" workaround like changing the DNS entry via OVH APIs before and after renewal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant