mirrors/TiddlyWiki5
1
0
Fork 0
mirror of https://github.com/Jermolene/TiddlyWiki5 synced 2025-04-14 14:53:20 +00:00
Code Issues Releases Wiki Activity

Merge ff1821cde98048281e18698ac91dc9bf5443e539 into 8bda28afd5082bbf3f77482990f476ca6764df17

Browse Source
This commit is contained in:
cmo-pomerium 2025-04-04 15:00:27 +02:00 committed by GitHub
commit e3aa5af9f9
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 1 deletions

7
editions/tw5.com/tiddlers/webserver/WebServer Header Authentication.tid

@ -8,6 +8,11 @@ Header authentication is a web integration technique enabling external entities
Header authentication is activated if is configured via the [[authenticated-user-header|WebServer Parameter: authenticated-user-header]]
!! 3rd Party Projects That Support This Mechanism
Pomerium, and open-source proxy, has [[a guide|https://www.pomerium.com/docs/guides/tiddlywiki]] for adding authentication and authorization to a TiddlyWiki instance.
!! Usage in SSO
Header authentication is commonly used for "single sign on" in corporate environments. When doing header authentication, the user is not prompted for a username and password on TiddlyWiki. Instead, the user is required to login at a SSO proxy server. When the user authenticates themselves to the SSO proxy server, the proxy server redirects the user request to the TiddlyWiki server with this additional request header containing the username. Then TiddlyWiki server is able to use the value of this request header to identify the user.
Header authentication is commonly used for "single sign on" in corporate environments. When doing header authentication, the user is not prompted for a username and password on TiddlyWiki. Instead, the user is required to login at a SSO proxy server. When the user authenticates themselves to the SSO proxy server, the proxy server redirects the user request to the TiddlyWiki server with this additional request header containing the username. Then TiddlyWiki server is able to use the value of this request header to identify the user.