-
Notifications
You must be signed in to change notification settings - Fork 2.8k
allow unauthorized role in accesskey and JWT modes (close #595) #856
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
Conversation
|
Review app available at: https://hge-ci-pull-856.herokuapp.com |
|
do not allow unauthorized role for webhook |
|
Review app available at: https://hge-ci-pull-856.herokuapp.com |
1 similar comment
|
Review app available at: https://hge-ci-pull-856.herokuapp.com |
server/src-lib/Hasura/Server/Auth.hs
Outdated
| where | ||
| unAuthRoleNotReqForWebHook = | ||
| when (isJust mUnAuthRole) $ | ||
| throwError $ "Fatal Error: --unauthorized-role (HASURA_GRAPHQL_UNAUTHORIZED_ROLE) is not required" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is not allowed
|
Review app available at: https://hge-ci-pull-856.herokuapp.com |
1 similar comment
|
Review app available at: https://hge-ci-pull-856.herokuapp.com |
|
Review app https://hge-ci-pull-856.herokuapp.com is deleted |
Description
--unauthorized-roleflag orHASURA_GRAPHQL_UNAUTHORIZED_ROLEenv variable can be specified (optional) in following modes:In access-key only mode, when the
x-hasura-access-keyis absent, the query will be executed using the role specified withunauthorized-roleoption. JWT mode will have the same behavior when theAuthorizationheader is absent in the request.unauthorized-roleoption is not required for Webhook mode.What component does this PR affect?
Requires changes from other components? If yes, please mark the components:
Related Issue
closes #595
Solution and Design
Type
Checklist: