Permissions for Remote Schemas
See original GitHub issuev1 (wip #2690):
Schema masking: Role-based types for query_root
, mutation_root
and subscription_root
fields
Deep schema masking: Role-based type for anything (object type, input object type, scalars?).
v2:
Input argument presets.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:20
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Remote Schema Permissions (Deprecated) - API Reference
Permissions for remote relationships are derived from the role's remote schema permissions. When permissions for a given remote relationship cannot be derived ...
Read more >Enforce Permissions via remote schema in Hasura
I'm unable to enforce Permissions via a Remote Schema Relationship. Is this possible to achieve with Hasura? I have a Remote Schema defined ......
Read more >Permissions (Database Engine) - SQL Server - Microsoft Learn
Base securable Granular permissions on base securable Securable that contains bas...
APPLICATION ROLE ALTER DATABASE
APPLICATION ROLE CONTROL DATABASE
APPLICATION ROLE VIEW DEFINITION DATABASE
Read more >Here's how you can use the upcoming Remote Schema...
Here's a look at how you can use the upcoming Remote Schema Permissions UI to extend Hasura's permission system to remote GraphQL APIs....
Read more >GRANT Statement (Access Control) - SAP Help Portal
A non-RESTRICTED user has the PUBLIC role, has the privileges required to create objects in their own default schema, and can grant privileges...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just wondering where this is sitting in the list of priorities? Thanks
My use case is to extend the same header-based role permissions that I use across Hasura to my remote schema, which doesn’t provide any usable access control other than CORS and tokens. I wish I could go into Data, see the entities from my Remote Schemas there, and be able to at least set high level query, mutation subscription permissions per entity. The closer it is to what Hasura does for it’s own tables, the better.