Information Security Asked by Harrison Lucas on October 29, 2020
So basically with my app, I keep users access tokens in memory for the duration page load (e.g. once they refresh the token dissapears). To prevent them from having to sign in again, I have my auth server (https://api.myapp.com
) set a httpOnly, secure cookie with a refresh token. This works fine for most users, however, some users are able to set custom domains, this means that the client react app is now on theirapp.com
and trying to auth with my api on api.myapp.com
. This still works in Chrome (latest), Firefox, and Safari Incognito, but does not work in normal safari (seems to completely ignore the refresh cookie).
What possible solutions do I have to making this work? Basically I want it so that:
theirapp.com
which makes a request to api.myapp.com
set-cookie:
header with a httpOnly; secure; domain; .myapp.com
refresh cookie. I want it so that this cookie is then sent when the user refreshes and the SPA react app makes a POST request to api.myapp.com/auth/refresh
. Is this possible in safari (again this works in all other browsers and even safari incognito)?
I don’t want to have to resort to storing a longer lived access token in the users localStorage or a non-httpOnly cookie as that’s obviously pretty vulernable to XSS.
When cookie A is set by api.myapp.com while the origin of the request is theirapp.com, then cookie A is treated as a third party cookie. Third party cookies were allowed by browsers until recently. Safari announced all third party cookies will be blocked by default. Both Firefox and Google will follow soon.
The suggestion from the said post which likely applies in your case is to use OAuth 2.0 authorisation. Or you could use OpenID connect (which is based on OAuth 2.0).
Answered by bhorkarg on October 29, 2020
Get help from others!
Recent Questions
Recent Answers
© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP