Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Cookie based authentication issues aggregation #23185
Provided in corresponding issues
Issues closed while still open. Cookie based authentication is at this moment not usable. This is partially due to the following issues:
These issues have been closed even though they are still open and very relevant.
In general cookie based authentication is very problematic on multiple levels. If cookie based authentication is
This is not a matter of pointing fingers or demanding features. It is currently unfortunately misleading to leave people unaware of all these limitations as they might set out to create an architecture that's unsupported as i have.
At the very least maybe we should revise the documentation of
I have the same issue as mentioned in #23005.
Example using postman:
Example RN iOS:
Example RN Android:
Surely. On the documentation found here:
Then I guess we should add in the docs, where we link to fetch, that cookies are not fully supported?
I mean, there is no direct reference to cookies in the RN docs so this phrase
is a bit passive-aggressive I feel
Have you tried using third-party libraries? Do they use fetch?
@kelset i apologise, implied is definitely a better word for it.
I hold immense respect both for you ( i am familiar with your contributions ) and the rest of the team and as i've already solved this issue by migrating to a token based architecture it is only for the purposes of helping others that i'm bringing this up.
How would you suggest proceeding from here? I can go ahead and edit the documentation referencing the corresponding issues but i am unaware of the processes as upon resolution documentation should be re-revisited.
Thanks so much for attending to this. Hopefully i will find some time to contribute to this issue myself.
As I mentioned above, probably the immediate step to be taken would be to clarify in the documentation that while we use
In the meantime for now I've added the "known issues" label which should help framing this problem in the right perspective.