Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Use integer for userId in JWT #3883

Closed
wants to merge 1 commit into from
Closed

Conversation

DafyddLlyr
Copy link
Contributor

@DafyddLlyr DafyddLlyr commented Oct 30, 2024

@DafyddLlyr DafyddLlyr force-pushed the dp/integer-userId-in-jwt branch from cabfdca to 3e9bd05 Compare October 30, 2024 19:42
Copy link

github-actions bot commented Oct 30, 2024

Removed vultr server and associated DNS entries

@DafyddLlyr
Copy link
Contributor Author

This isn't the right way forward here, according to the docs -

Session variables are currently expected to only be strings and should be encoded based on Postgres's literals for the relevant type.

Source: https://hasura.io/docs/2.0/auth/authorization/roles-variables/

Hasura should be casting this correctly, the insert error I'm getting when trying to use the demoUser role must be coming from somewhere else. Looking into it atm!

@DafyddLlyr DafyddLlyr closed this Oct 31, 2024
@DafyddLlyr DafyddLlyr deleted the dp/integer-userId-in-jwt branch October 31, 2024 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant