OpenIdDict 2 (16.12.2022 M)

Question 1

What does AddCore make and why do you need to call options.UseEntityFrameworkCore()
.UseDbContext<DbContext>();</DbContext>

Answer 1

AddCore registers core services, for example, managers and store resolvers of the Application, Authorization, Scopes, and Token entities.
So the aim of the Core is to provide access to and management of Application, Authorization, Scopes, and Token entities.

You need to call UseEntityFrameworkCore to register stores that will be resolved by resolvers (you add EF implementation of stores).

Question 2

What are ephemeral keys?

Answer 2

You can use ephemeral keys for encrypting or signing tokens

Ephemeral keys are automatically discarded when the application shuts down and payloads signed or encrypted using these keys are therefore automatically invalidated. This method should only be used during development.

On production, using a X.509 certificate is recommended

Question 3

What does AddServer make?

Answer 3

OpenIdDict is implemented with the Mediator pattern.

So AddServer registers the dispatcher and a bunch of default handlers, which implement main business logic, like handling the validation of OAuth + OpenId endpoints requests, preparing responses for them, etc.

AddServer allows configuring of server behavior and data. For example, you can add scopes here, set issuer host, set up keys for encryption and digital signature, and set up endpoints URLs.

Question 4

What UseAspNetCore does do inside AddServer?

Answer 4

AddServer registers like business logic, when UseAspNetCore connects it with the AspNetCore pipeline.

Question 5

What middleware does UseAspNetCore use for integration to the pipeline?

Answer 5

It uses Authentication middleware. It means that to make OpenIdDict work you have to call UseAuthentication between UseRouting and UseEndpoints.