FAQ
Tyke is a gateway that includes built-in features for securing GraphQL endpoints, such as authorization mechanisms, query depth limiting, and field-based permissions. It allows users to proxy to existing GraphQL services and add security features directly through its dashboard.
Tyke provides several security features for GraphQL APIs including built-in authorization, schema security through field-based permissions, and protection against denial of service attacks by adding query depth limiting.
Query depth limiting is a security measure used to prevent denial of service attacks by restricting the complexity of queries that can be executed against a GraphQL API. It limits the depth of queries to prevent excessively deep and resource-intensive queries.
Authorization in GraphQL via Tyke is enforced by proxying an existing GraphQL API through Tyke and configuring authorization settings in the Tyke dashboard. This setup requires an authentication token to access the proxied API, ensuring that only authorized users can execute queries.
Field-based permissions in GraphQL security involve specifying access controls at the field level within a GraphQL schema. This ensures that only designated users or roles have the access rights to specific fields, enhancing data privacy and compliance.
Yes, Tyke can manage multiple GraphQL services and has mechanisms to resolve naming conflicts that may arise when integrating multiple APIs. This includes manual workarounds and upcoming features intended to streamline conflict resolution.
Query depth refers to how deep a GraphQL query can go. Tyke controls this by allowing administrators to set maximum query depths, which can vary by user group, thereby preventing excessively deep queries that could impact performance or security.
Comments