diff --git a/configuration/application-permissions.html b/configuration/application-permissions.html index 5a73cce..acf8b21 100644 --- a/configuration/application-permissions.html +++ b/configuration/application-permissions.html @@ -283,8 +283,8 @@ if (await manager.FindByClientIdAsync("console") is null) options.IgnoreScopePermissions(); });

Response type permissions

-

-> [!NOTE] --> Response type permissions were introduced in OpenIddict 3.0.

+
Note

Response type permissions were introduced in OpenIddict 3.0.

+

Definition

Response type permissions limit the response types a client application is allowed to use when implementing an interactive flow like code, implicit or hybrid.

Supported permissions

diff --git a/guide/getting-started.html b/guide/getting-started.html index 2618636..76d7b73 100644 --- a/guide/getting-started.html +++ b/guide/getting-started.html @@ -171,31 +171,26 @@ Here's an example for the client credentials grant, used in machine-to-machi // to replace the default OpenIddict entities. options.UseOpenIddict(); }); - - -

-> [!WARNING] --> Important: if you change the default entity primary key (e.g. to int or Guid instead of string), make sure you use the options.ReplaceDefaultEntities<TKey>() --> core extension accepting a TKey generic argument and use the generic options.UseOpenIddict<TKey>() overload to configure EF Core to use the specified type: --> --> csharp --> services.AddOpenIddict() --> .AddCore(options => --> { --> // Configure OpenIddict to use the default entities with a custom key type. --> options.UseEntityFrameworkCore() --> .UseDbContext<ApplicationDbContext>() --> .ReplaceDefaultEntities<Guid>(); --> }); --> --> services.AddDbContext<ApplicationDbContext>(options => --> { --> // Configure the context to use Microsoft SQL Server. --> options.UseSqlServer(configuration["Data:DefaultConnection:ConnectionString"]); --> --> options.UseOpenIddict<Guid>(); --> }); -->

-