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
What is the impact of removing this feature? Would it just disable SessionManagement? If the customer does not use Session Mgt, they may not care, and may prefer to use HTTPOnly. In this case, it would be better to maintain a JSON property that made this flag configurable.
Customer commented:
> The cookie Session_state is served with httponly=false which
> is a potential security risk. I found in the code of
> SessionStateService.java a comment stating it's not possible to set
> this to true due to the fact it is read by javascript.
The text was updated successfully, but these errors were encountered:
Support JSON Property for HTTPOnly
To enable it, set sessionStateHttpOnly: true in oxAuth config.
Note that SessionManagement will not work.
See http://openid.net/specs/openid-connect-session-1_0.html
Note that your browser should not allow a client-side script to access the session_state cookie. Unfortunately, since the attribute is relatively new, several browsers may neglect to handle the new attribute properly.
See https://www.owasp.org/index.php/HttpOnly
Using HTTPOnly would mitigate the risk of the session being stolen. See: https://www.owasp.org/index.php/HttpOnly
What is the impact of removing this feature? Would it just disable SessionManagement? If the customer does not use Session Mgt, they may not care, and may prefer to use HTTPOnly. In this case, it would be better to maintain a JSON property that made this flag configurable.
Customer commented:
The text was updated successfully, but these errors were encountered: