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
I have to take in mind how to keep XRSF security and how to handle it without session. I think we can simply store needed information inside JWT token but I have to check.
Moreover api-gateway also create a session for XRSF it will be good to avoid it if possible.
Or if not switch to spring-session with dedicated store like redis
@yaytul What is your use case? If you are going for a single page app with a set of ReST APIs and the resource owner credentials flow then you can remove the XSRF protection since it doesn't apply to ReST API. That would remove the need for the stateful HttpSessionCsrfTokenRepository.
As per discussion in issue #16, please refrain from using Http Session and make Authentication work stateless.
The text was updated successfully, but these errors were encountered: