mirror of
https://github.com/Jermolene/TiddlyWiki5
synced 2024-12-02 14:29:55 +00:00
If applied, this commit will give users a link to an open-source guide
This commit is contained in:
parent
72a4adbd6b
commit
8ddcf72919
@ -8,6 +8,8 @@ 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]]
|
||||
|
||||
Here is an [example guide](https://www.pomerium.com/docs/guides/tiddlywiki) of how to add authentication and authorization to a TiddlyWiki instance with Pomerium, an open-source proxy.
|
||||
|
||||
!! 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.
|
||||
|
Loading…
Reference in New Issue
Block a user