Skip to content

Commit

Permalink
wip
Browse files Browse the repository at this point in the history
  • Loading branch information
seanparkross committed Jan 17, 2025
1 parent 98c965e commit 5636453
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions docs/auth/private-vs-public.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,11 +21,13 @@ You can choose to make your Hasura DDN API public or private.
A `private` Hasura DDN API is only accessible to collaborators on your project.

Queries to a private Hasura DDN API must include a special reserved header `x-hasura-ddn-token` with a valid JWT token
which the Hasura console generates and regenerates every hour.
which the Hasura console generates and regenerates every hour. Currently this token is only available in the console.

If a `private` API is also set to JWT or Webhook mode, rather than `noAuth` mode, queries must **also** include the JWT
or webhook authentication values to be successful in addition to the `x-hasura-ddn-token` header.

Projects set to `private` mode are not meant to be used in production.

## Public

A public Hasura DDN API is accessible to everyone.
Expand All @@ -43,7 +45,7 @@ If set to `public` with `noAuth` mode, queries do not require any authentication

## Changing the API mode

### DDN client
### DDN CLI

Set to `private` mode:

Expand Down

0 comments on commit 5636453

Please sign in to comment.