
SamiB.72222 (Customer) asked a question.
Hello,
Our Security team is raising a warning about okta cookies not being flagged as HttpOnly, this is can prevent us to use Okta in future.
Is there any particular reason for not flagging these cookies as HttpOnly?
Thanks.
Sami

Hello @SamiB.72222 (Customer) Thank you for reaching out to our community.
Please see our similar question on Developer forum which should answer your question:
https://devforum.okta.com/t/cookies-without-secure-and-http-flag-set/3540
My advice would be to leverage the Okta Developer forums for this type of questions and take advantage of their expertise.
https://devforum.okta.com/
Hello @Paul S. (Okta, Inc.)
Our company has exactly the same question, we would really appreciate it if you can clarify it.
Same as Sami said, the question is particularly about okta-oauth-* cookies.
Many thanks,
Kon
Hi @Paul S. (Okta, Inc.)
A recent PEN test of the application I work on has also raised questions about HttpOnly on okta-oauth-* cookies.
Clarification on this would be greatly appreciated.
Thanks,
Jaimie
I also asked about this on the devforum.
I got the following answer from bdemers (from the Okta team):
Setting cookies to HttpOnly would prevent JavaScript from reading the value. If you are building a SPA application, the JS must have access to these values (as that is where the auth flow starts)
Hello Paule,
Thanks for your answer, we've already found that forum thread but it doesn't answer fully our question.
In our case these cookies “okta-oauth-state” “okta-oauth-nonce” “okta-oauth-redirect-params" are not flagged as HttpOnly which are more sensitive than JSESSIONID cookie
Thanks
Sami