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
For example, if I want to grant SELECT permission of specific table to Unauthenticated users, we need to define permissions to a unauthorized role ( let's say incognito )
Then set HASURA_GRAPHQL_UNAUTHORIZED_ROLE or the --unauthorized-role to incognito for graphql-engine server.
currently HASURA_GRAPHQL_UNAUTHORIZED_ROLE=public preset in generated docker-compose.yaml by nhost cli and not customizable.
would be nice if we can customizable this flag in nhost.toml
Hello, thanks for the request, what is the difference between calling the role public or incognito though? what is the use case to be able to change the name?
As per documentation here: Unauthenticated request definitions, we can use hasura environment variable to customize unauthorized role.
For example, if I want to grant
SELECT
permission of specific table to Unauthenticated users, we need to define permissions to a unauthorized role ( let's say incognito )Then set
HASURA_GRAPHQL_UNAUTHORIZED_ROLE
or the --unauthorized-role
toincognito
forgraphql-engine
server.currently
HASURA_GRAPHQL_UNAUTHORIZED_ROLE=public
preset in generateddocker-compose.yaml
bynhost cli
and not customizable.would be nice if we can customizable this flag in
nhost.toml
The text was updated successfully, but these errors were encountered: