August 2019 Summaries

This article discusses how to use Hasura Remote Joins to join data from your Postgres database with user data in Okta. It explains that Data Federation using Hasura Remote Joins is now available in v1.3.0 stable release and can be tried out on Hasura Cloud. The author provides an example of joining Okta's API with a Postgres table called "users" to fetch user information. They also mention other posts in the Remote Joins series that explore more use-cases and possibilities for application development.

The v1.0.0-beta.3 release introduced enhancements to the GraphQL engine's logs, including startup, http-log, webhook-log, and websocket-log types. These log types are now enabled by default, with detailed documentation available. Additionally, query-log was introduced but is not enabled by default; it can be set using an environment variable. An example of each log type is provided, along with a changelog for more information on the changes.

In v1.0.0-beta.3, support for array operators like _in, _nin, and _has_keys_any has been added to permission rules. This feature allows users to specify access permissions based on arrays of values. An example is given where a user can access zero, one or several organizations. The session variable X-Hasura-Allowed-Org-Ids contains an array of org_id values that determine which organizations the user has access to. The array operators are useful for managing complex permission scenarios and provide more flexibility in defining access control rules.

The latest release of Hasura Console introduces a JWT Analyzer feature. Previously, decoding JWTs required an external tool like jwt.io. This new feature allows users to analyze and decode tokens directly within the console. To use this feature, obtain a valid JWT token from any provider and add it to the Authorization request header in Hasura's GraphiQL page. Clicking on the rectangular icon will open the analyzer, displaying information about the token's validity, Hasura claims, headers, and full payload. This update aims to improve user experience by simplifying JWT handling within the console.

This article discusses how to join data from a Postgres database with serverless data in FaunaDB using Hasura Remote Joins. It explains that Data Federation using Hasura Remote Joins is now available starting from the v1.3 beta release. The author demonstrates an example of joining a schema in FaunaDB with existing data in Hasura, assuming there is a users table in Hasura with columns id and name. The process involves creating a GraphQL Schema in FaunaDB, inserting sample data, obtaining an access key, adding FaunaDB as a Remote Schema in the Hasura Console, and setting up relationships between tables. Finally, it provides a GraphQL query to fetch this data in a single API call.

This post discusses how Hasura Remote Joins can be used to join data from a Postgres database with any OpenAPI/Swagger compliant REST API. The example provided demonstrates joining users table data in Postgres with exchange rate data from an OpenAPI service, which is a currency exchange rate API. By adding the OpenAPI service as a Remote Schema using Hasura Console and creating a remote relationship called "currency_rates," it becomes possible to query both sets of data in a single API call. The GraphQL query for this operation includes nested queries from the exchange rate API, which filters the results based on the user's currency.

In this tutorial, we will create an authentication solution for Hasura using Netlify. The main difference between this and previous solutions is that Netlify Identity supports JWT but does not support custom claims, which are crucial to make Hasura work with JWT tokens. We will use a custom Auth webhook to verify the JWT token provided by Netlify Identity, extract data from it, and send this data in a format Hasura can parse and use in its permission system. The tutorial covers setting up Hasura on Heroku, creating two tables (posts and users), getting users into Hasura, creating a Netlify site, and creating signup and custom auth webhooks. It also discusses signing in with Google or other providers and provides a summary of the live coding solution for real-world problems.