vh/homepage
1
0
Fork 0
mirror of https://github.com/gethomepage/homepage.git synced 2026-08-31 01:15:53 -07:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

Documentation: tweak auth docs

Browse Source
This commit is contained in:
shamoon
2026-06-13 08:12:32 -07:00
parent 8beac702ea
commit ce7594d058
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -66,7 +66,7 @@ For configuration options, examples and more, [please check out the homepage doc
Please note that when using features such as widgets, Homepage can access personal information (for example from your home automation system). To keep your information private, if Homepage is reachable from any untrusted network, it:
1. **must** sit behind a reverse proxy (and/or VPN) that enforces authentication, TLS, and strictly validates Host headers.
2. An optional built-in OIDC login flow is available (opt-in) offering a simple “authenticated or not” guard.
2. An optional built-in OIDC login flow or simple password login is available (opt-in) offering a simple “authenticated or not” guard.
## With Docker
docs/installation/index.md
+1 -1
View File
@@ -60,4 +60,4 @@ For OIDC login (overrides password login):
- `HOMEPAGE_EXTERNAL_URL` (external URL to your Homepage instance; used for callbacks)
- Optional: `HOMEPAGE_OIDC_NAME` (display name), `HOMEPAGE_OIDC_SCOPE` (defaults to `openid email profile`)
All app pages and `/api` routes will require a signed-in session. Static assets remain public. Homepage still does not implement per-user dashboards or roles; authentication is a simple gate only.
All app pages and `/api` routes will require a signed-in session. Static assets remain public.