Query as an @auth option about graphql

[danstarns]

Hey @tlester thanks for subbmitng your idea! Im struggling to get the concept do you have any more examples or info ? Given the below:

type User {
  name: String
}

extend type User @auth(rules: [{ 
    operations: [CREATE],
    isAuthenticated: true,
    query: {
        match: "allen",
        gql:  `users(where: {name: "bob"}) { name }`
    }
}])

Then someone performs a CREATE operation:

mutation {
  createUsers(input: [{ name: "SOME NAME" }]) {
    users {
      name
    }
  }
}

Where and how does the below query bit get incorporated with this mutation?

query: {
        match: "allen",
        gql:  `users(where: {name: "bob"}) { name }`
    }

[darrellwarde]

I need to have a flexible option validate date as a condition for authenticity.

I find myself especially intrigued by this use case, an example of how and where you might use this could really provide some clarity here.

[bloomdido]

@tlester Would my suggested feature #163 satisfy your needs? The @cypher directive can already handle parameters, and you'd have full access to the power of Cypher (not just GraphQL) in determining the conditions for your validation.

[jacob-buscher]

I need to have a flexible option validate date as a condition for authenticity.

I find myself especially intrigued by this use case, an example of how and where you might use this could really provide some clarity here.

@darrellwarde

This would be especially useful in places where you need tenant based auth, if you have numerous "organizations" and "suborganizations" and you want to have RBAC style roles

Something like ${teamId}:admin, ${teamId}:owner, ${teamId}:guest where teamId is populated from based on the query.

I'm having a hard time using the @auth directive to make tenant based roles and permissions. I believe this is possible with allow but my rules are looking way more complex than I think they should.

I go into a bit of detail about my use case in #163

[darrellwarde]

This is not something we're ever going to do - auth is a big enough beast as it is and is overdue a much needed refactor, but GraphQL within a directive definitely won't be a part of it - far too meta!! 😆 In the interest in making some progress on the feature backlog, closing this one.