You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2022. It is now read-only.
Describe the bug
After struggling to get example client to work, decided to focus on core functions.
Deploying app per instructions; when I use Hasura api explorer, and use ‘authorization’ header with Bearer deduced from keycloak login, connector always seems to fail validation of token, and returning Anonymous role string
To Reproduce
Steps to reproduce the behavior:
Go to 'Hasura ./auth/realm/master/account' and login. Inspect headers to get bearer token.
Inspect to insure it has appropriate realm roles.
In Hasura api explorer, use authorization header.
Attempt query. If Defined anonymous role doesn’t have access, an error results
See error
Expected behavior
Bearer token privileges are confirmed
Screenshots
Desktop (please complete the following information):
attempted in local docker and kibernetes environments
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
After struggling to get example client to work, decided to focus on core functions.
Deploying app per instructions; when I use Hasura api explorer, and use ‘authorization’ header with Bearer deduced from keycloak login, connector always seems to fail validation of token, and returning Anonymous role string
To Reproduce
Steps to reproduce the behavior:
Inspect to insure it has appropriate realm roles.
Expected behavior
Bearer token privileges are confirmed
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: