@@ -29,7 +29,7 @@ side cookies and transferred with each and every request.
29The following should be known when using this implementation:
29The following should be known when using this implementation:
30- Since all state is stored client side, this storage backend means that the OAuth2 Proxy is completely stateless
30- Since all state is stored client side, this storage backend means that the OAuth2 Proxy is completely stateless
31- Cookies are signed server side to prevent modification client-side
31- Cookies are signed server side to prevent modification client-side
32−- It is recommended to set a `cookie-secret` which will ensure data is encrypted within the cookie data.
32+- It is mandatory to set a `cookie-secret` which will ensure data is encrypted within the cookie data.
33- Since multiple requests can be made concurrently to the OAuth2 Proxy, this session implementation
33- Since multiple requests can be made concurrently to the OAuth2 Proxy, this session implementation
34cannot lock sessions and while updating and refreshing sessions, there can be conflicts which force
34cannot lock sessions and while updating and refreshing sessions, there can be conflicts which force
35users to re-authenticate
35users to re-authenticate