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
As I am digging into mesh further I am delighted by some of the things it can do but at the same time have open questions.
Is there a recommended way to control and authorize graphql query operation in mesh.
For example, using a database as source, it would not always be desired that users access every table and record.
Is there a way to pass a role to graphql-mesh and define access restrictions, e.g. role of editor can call mutation x while role of user can only read their own records from table?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Team:
As I am digging into mesh further I am delighted by some of the things it can do but at the same time have open questions.
Is there a recommended way to control and authorize graphql query operation in mesh.
For example, using a database as source, it would not always be desired that users access every table and record.
Is there a way to pass a
role
to graphql-mesh and define access restrictions, e.g. role ofeditor
can call mutation x while role ofuser
can only read their own records from table?Could this be defined in
.meshrc.yaml
?Cheers,
Bilal
Beta Was this translation helpful? Give feedback.
All reactions