From 4ac33e63bb27ce397f54818567d9d394e7aadedb Mon Sep 17 00:00:00 2001 From: OpenIddict Bot <32257313+openiddict-bot@users.noreply.github.com> Date: Wed, 13 Jan 2021 05:02:24 +0000 Subject: [PATCH] Update the documentation pages --- guide/getting-started.html | 6 ++++-- manifest.json | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/guide/getting-started.html b/guide/getting-started.html index 5b7117c..2618636 100644 --- a/guide/getting-started.html +++ b/guide/getting-started.html @@ -171,7 +171,9 @@ Here's an example for the client credentials grant, used in machine-to-machi // to replace the default OpenIddict entities. options.UseOpenIddict(); }); -
-> [!WARNING] + + +
-> [!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:
->
@@ -193,7 +195,7 @@ Here's an example for the client credentials grant, used in machine-to-machi
-> options.UseOpenIddict<Guid>();
-> });
->
Create your own authorization controller: Implementing a custom authorization controller is required to allow OpenIddict to create tokens based on the identities and claims you provide. Here's an example for the client credentials grant:
diff --git a/manifest.json b/manifest.json index 7e26c7a..0cdd8b1 100644 --- a/manifest.json +++ b/manifest.json @@ -45,7 +45,7 @@ "output": { ".html": { "relative_path": "guide/getting-started.html", - "hash": "x2y3JmMShZP8OKbVIkktGw==" + "hash": "PAK5Gf5at4cqxIPy5Io9pg==" } }, "is_incremental": false,