Skip to content
This repository has been archived by the owner on Feb 24, 2024. It is now read-only.

Tutorial for login with jwt/sessions #240

Open
steve-chavez opened this issue Aug 2, 2019 · 2 comments
Open

Tutorial for login with jwt/sessions #240

steve-chavez opened this issue Aug 2, 2019 · 2 comments
Labels
tutorials Learning oriented guides, hand-holding for new users.

Comments

@steve-chavez
Copy link
Member

See if we can use the example in PostgREST/postgrest#664

@steve-chavez steve-chavez added the tutorials Learning oriented guides, hand-holding for new users. label Aug 15, 2019
@steve-chavez
Copy link
Member Author

Right now there are good snippets in http://postgrest.org/en/v5.2/auth.html#logins and they have been working good. But seems the section is a mix of an explanation and how-to. I'm thinking we could turn this into a tutorial 3. After the RLS one, which I'm thinking it could be separate from login.

@mckinlde
Copy link

mckinlde commented Nov 13, 2023

Right now there are good snippets in http://postgrest.org/en/v5.2/auth.html#logins and they have been working good. But seems the section is a mix of an explanation and how-to. I'm thinking we could turn this into a tutorial 3. After the RLS one, which I'm thinking it could be separate from login.

Hi, I'm a novice end user. I was able to get from tutorial 1 to storing the JWT from an Authorization header in session storage pretty easily, but after lots of reading the closest I can get to storing JWTs in cookies is via a reverse proxy. It seems like I'm not the only userwith this problem; is it even possible as of now to run pgRest's auth/auth JWTs via cookies? Or is a reverse proxy required? If I were to use a reverse proxy, then it would be running for the sole purpose of translating between Http Only SameSite cookies and the Authorization Bearer= header.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
tutorials Learning oriented guides, hand-holding for new users.
Development

No branches or pull requests

2 participants