graphql-shield | A GraphQL tool to ease the creation of permission layer | GraphQL library

I'm using graphql-shield on a subgraph and rover-cli to generate the schema.

I've set the fallback rule to deny everything as I don't want anything to be accessible by default. But now rover-cli fails when introspecting the subgraph. I'm aware that you can pass a token to rover but I'm unable to do so during my build process.

I've already looked at this issue: Apollo Server Federation with graphql-shield and on both graphql-shield & rover GitHub repository but not luck so far.

I've also tried to explicitly add SubgraphIntrospectQuery like so:

I have a project where I have updated all of the packages.

Before the update all e2e tests functioned as expected.

After the update, The product itself compiles and runs as expected.

However, the e2e tests are showing unexpected issues both in the IDE and at run time.

For example,

I am running Mongoose and exposing an API using GraphQL (Apollo).

I want to implement a RBAC and after some research I came with a solution using CASL and graphql-shield. Ideally, I would then want to share the rules with my React front-end.

First step, planning on a piece of paper.

I would first define my actions: Create, Read, Update, Delete.

Then I would define my subjects: Car, Motorcycle.

After that is done I would proceed to define my roles: CarSpecialist, MotoSpecialist, Admin. I would then define some conditions: "subject is my own", etc..

Finally, I would assign to each role, a set of abilities (combination of action, subject, conditions).

Now with all this done, I start actually coding my solution.

I start by writing the abilities in CASL: actions and subjects are pretty straightforward to define.

Conditions are a bit trickier and I have at least two options:

• I use "vague" notions that in turn have to be interpreted by whatever needs to enforce them (back or front end).

• I use the CASL mongoose integration plugin, at the cost of losing the ability to share with my frontend.

Any input on which to choose?

Now once CASL abilities are defined, is it up to graphql-shield to enforce them?

How do I do the mapping between (CASL) actions, subjects and conditions to graphql terms: Schema, Query, Mutations ...?

I'm new to Docker, and I've wanted try Dockerizing my node app.

I've tried following the directions on nodejs.org, but I've been getting errors on npm install.

Here is my Dockerfile: