Find solution for developing in graphiql with RLS-Auth in place #4

New issue

Closed

opened 2020-05-30 15:17:34 +02:00 by peter.mueller · 1 comment

peter.mueller commented

2020-05-30 15:17:34 +02:00

(Migrated from git.verdigado.com)

When RLS-Auth ist in place the graphiql frontend for testing and building queries is not available out of the box. There are some possibilities to solve this problem.

See this Github issue for more information about the possibilities.

For us we have to decide:

should we provide a solution in this repo (maybe by starting a docker container)
or just a recommendation so that every dev can have his/her own solution
Have a dev mode where rls is deactivated and only in production rls is activated

Let's discuss on that :-)

When RLS-Auth ist in place the graphiql frontend for testing and building queries is not available out of the box. There are some possibilities to solve this problem. See [this Github issue](https://github.com/graphql/graphiql/issues/59) for more information about the possibilities. For us we have to decide: * should we provide a solution in this repo (maybe by starting a docker container) * or just a recommendation so that every dev can have his/her own solution * Have a dev mode where rls is deactivated and only in production rls is activated Let's discuss on that :-)

christoph.lienhard commented

2020-05-30 23:49:21 +02:00

(Migrated from git.verdigado.com)

Luckily there is the postgraphile option --enhance-graphiql wich is perfectly fine in dev mode. It deploys a much more feature-rich graphiql version which, most importantly includes a headers section.

Authentication in graphiql resolves to calling the authenticate mutation and copying the jwt string into the header section.

This change is included in #3

From my point of view, this issue is thereby resolved.

Luckily there is the postgraphile option `--enhance-graphiql` wich is perfectly fine in dev mode. It deploys a much more feature-rich graphiql version which, most importantly includes a headers section. Authentication in graphiql resolves to calling the authenticate mutation and copying the jwt string into the header section. This change is included in #3 From my point of view, this issue is thereby resolved.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: NB-Public/kandimat#4

No description provided.