Move GraphQLAuthExtensions from Harness into new package about authorization HOT 6 CLOSED

If OK, I want to add this feature in v5.

from authorization.

I looked at the two methods within GraphQLAuthExtensions.cs file under Harness. It seems to me that they only need access to GraphQL.DI.IGraphQLBuilder as there is no MS-DI or ASP.Net-specific methods contained in there. These methods should be added to the current version of GraphQL.Authorization, without waiting for v5, as GraphQL.DI.IGraphQLBuilder was included in GraphQL.NET 4.6. I would not create another nuget package.

from authorization.

GraphQL.DI.IGraphQLBuilder 🤔 ? Is this a new project? I have not seen yet, 500 emails :(.

from authorization.

See https://graphql-dotnet.github.io/docs/getting-started/dependency-injection#dependency-injection-registration-helpers

Added and revised in:

• graphql-dotnet/graphql-dotnet#2571
• graphql-dotnet/graphql-dotnet#2607
• graphql-dotnet/graphql-dotnet#2612

from authorization.

Basically, it allows 3rd party libraries such as GraphQL.Authorization to do the following all within a single IGraphQLBuilder method:

• Register services within the user's DI framework (any DI framework, and without a dependency)
• Configure options using the options configuration pattern (without a dependency on the MS options pattern)
• Configure schema options
• Configure execution options

In this case, the new AddAuthorization method does 3 of the 4 listed above:

• Configures authorization options based on the provided delegate
• Registers necessary classes within the DI framework
• Adds the authorization validation rule during execution

from authorization.

@sungam3r Check out this sample which uses the new IGraphQLBuilder approach:

https://github.com/graphql-dotnet/graphql-dotnet/blob/master/src/GraphQL.Harness/Startup.cs#L30..L51

from authorization.