Skip to content

How to implement remix-auth true webapi? Mobile client #240

Closed Answered by sergiodxa
Jarrodsz asked this question in Q&A
Discussion options

You must be logged in to vote

Remix Auth depends on the Remix's sessions, which at the same time uses cookies either to store the whole session data or to store a session ID.

In a mobile app there's no cookies, and while you could send the Cookie header yourself, it's not the normal.

My recommendation is to don't use Remix Auth for an API, instead attach a token to each request using the Authorization header and then create a function that you can pass the request and can check if the header is set, there's a token and it's still valid.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by sergiodxa
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants