You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If Satosa is installed under a path which is not the root of the
webserver (ie. "https://example.com/satosa"), then endpoint routing must
take the base path into consideration.
Some modules registered some of their endpoints with the base path
included, but other times the base path was omitted, thus it made the
routing fail. Now all endpoint registrations include the base path in
their endpoint map.
Provide a simple implementation for joining path components, since we
don't want to add the separator for empty strings and when any of the
path components already have it.
Additionally, DEBUG logging was configured for the tests so that the
debug logs are accessible during testing.
|`BASE`| string |`https://proxy.example.com`|The base url of the proxy. For the OIDC Frontend, this is used to set the issuer as well, and due to implementation constraints, avoid using trailing slashes in this case. |
81
+
|`BASE`| string |`https://proxy.example.com`| base url of the proxy |
82
82
|`COOKIE_STATE_NAME`| string |`satosa_state`| name of the cookie SATOSA uses for preserving state between requests |
83
83
|`CONTEXT_STATE_DELETE`| bool |`True`| controls whether SATOSA will delete the state cookie after receiving the authentication response from the upstream IdP|
84
84
|`STATE_ENCRYPTION_KEY`| string |`52fddd3528a44157`| key used for encrypting the state cookie, will be overridden by the environment variable `SATOSA_STATE_ENCRYPTION_KEY`if it is set|
0 commit comments