@@ -29,7 +29,7 @@ side cookies and transferred with each and every request.
2929The following should be known when using this implementation:
3030- Since all state is stored client side, this storage backend means that the OAuth2 Proxy is completely stateless
3131- 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.
3333- Since multiple requests can be made concurrently to the OAuth2 Proxy, this session implementation
3434cannot lock sessions and while updating and refreshing sessions, there can be conflicts which force
3535users to re-authenticate