Currently, OIDC access tokens are stored in sessionStorage, which exposes security vulnerabilities, especially in light of OWASP recommendations.
Security Concerns
XSS Vulnerability: Tokens in sessionStorage are accessible to JavaScript, making them vulnerable to theft via XSS attacks.
Token Theft Risk: Client-side storage in sessionStorage increases the risk of unauthorized token access and reuse.
Recommendation
To improve security, consider storing access tokens in memory rather than sessionStorage. This reduces the attack surface and aligns with OWASP's guidelines for secure client-side token handling.
Currently, OIDC access tokens are stored in sessionStorage, which exposes security vulnerabilities, especially in light of OWASP recommendations.
Security Concerns XSS Vulnerability: Tokens in sessionStorage are accessible to JavaScript, making them vulnerable to theft via XSS attacks. Token Theft Risk: Client-side storage in sessionStorage increases the risk of unauthorized token access and reuse.
Recommendation To improve security, consider storing access tokens in memory rather than sessionStorage. This reduces the attack surface and aligns with OWASP's guidelines for secure client-side token handling.