Update the documentation pages

This commit is contained in:
OpenIddict Bot 2021-01-13 04:59:49 +00:00
parent 8263d95312
commit 4edb932430
3 changed files with 27 additions and 28 deletions

View File

@ -283,9 +283,8 @@ if (await manager.FindByClientIdAsync("console") is null)
options.IgnoreScopePermissions();
});
</code></pre><h2 id="response-type-permissions">Response type permissions</h2>
<p>-&gt; [!NOTE]</p>
<blockquote><p>Response type permissions were introduced in OpenIddict 3.0.</p>
</blockquote>
<p>-&gt; [!NOTE]
-&gt; Response type permissions were introduced in OpenIddict 3.0.</p>
<h3 id="definition-3">Definition</h3>
<p>Response type permissions limit the response types a client application is allowed to use when implementing an interactive flow like code, implicit or hybrid.</p>
<h3 id="supported-permissions-3">Supported permissions</h3>

View File

@ -171,29 +171,29 @@ Here&#39;s an example for the client credentials grant, used in machine-to-machi
// to replace the default OpenIddict entities.
options.UseOpenIddict();
});
</code></pre></li>
</ul>
<p>-&gt; [!WARNING]</p>
<blockquote><p>Important: if you change the default entity primary key (e.g. to <code>int</code> or <code>Guid</code> instead of <code>string</code>), make sure you use the <code>options.ReplaceDefaultEntities&lt;TKey&gt;()</code>
core extension accepting a <code>TKey</code> generic argument and use the generic <code>options.UseOpenIddict&lt;TKey&gt;()</code> overload to configure Entity Framework Core to use the specified key type:</p>
<pre><code class="lang-csharp">services.AddOpenIddict()
.AddCore(options =&gt;
{
// Configure OpenIddict to use the default entities with a custom key type.
options.UseEntityFrameworkCore()
.UseDbContext&lt;ApplicationDbContext&gt;()
.ReplaceDefaultEntities&lt;Guid&gt;();
});
services.AddDbContext&lt;ApplicationDbContext&gt;(options =&gt;
{
// Configure the context to use Microsoft SQL Server.
options.UseSqlServer(configuration[&quot;Data:DefaultConnection:ConnectionString&quot;]);
options.UseOpenIddict&lt;Guid&gt;();
});
</code></pre></blockquote>
<ul>
</code></pre><p>-&gt; [!WARNING]
-&gt; Important: if you change the default entity primary key (e.g. to <code>int</code> or <code>Guid</code> instead of <code>string</code>), make sure you use the <code>options.ReplaceDefaultEntities&lt;TKey&gt;()</code>
-&gt; core extension accepting a <code>TKey</code> generic argument and use the generic <code>options.UseOpenIddict&lt;TKey&gt;()</code> overload to configure EF Core to use the specified type:
-&gt;
-&gt; <code>csharp
-&gt; services.AddOpenIddict()
-&gt; .AddCore(options =&gt;
-&gt; {
-&gt; // Configure OpenIddict to use the default entities with a custom key type.
-&gt; options.UseEntityFrameworkCore()
-&gt; .UseDbContext&lt;ApplicationDbContext&gt;()
-&gt; .ReplaceDefaultEntities&lt;Guid&gt;();
-&gt; });
-&gt;
-&gt; services.AddDbContext&lt;ApplicationDbContext&gt;(options =&gt;
-&gt; {
-&gt; // Configure the context to use Microsoft SQL Server.
-&gt; options.UseSqlServer(configuration[&quot;Data:DefaultConnection:ConnectionString&quot;]);
-&gt;
-&gt; options.UseOpenIddict&lt;Guid&gt;();
-&gt; });
-&gt;</code></p>
</li>
<li><p><strong>Create your own authorization controller:</strong>
Implementing a custom authorization controller is required to allow OpenIddict to create tokens based on the identities and claims you provide.
Here&#39;s an example for the client credentials grant:</p>

View File

@ -9,7 +9,7 @@
"output": {
".html": {
"relative_path": "configuration/application-permissions.html",
"hash": "bn2oc9vnYnRCNd31rO4mnw=="
"hash": "T82L6dl/gd6zRNmoTwudtw=="
}
},
"is_incremental": false,
@ -45,7 +45,7 @@
"output": {
".html": {
"relative_path": "guide/getting-started.html",
"hash": "EubGbQd6qMqQ/UD3oj2WIw=="
"hash": "G5Z0qYgQEEbzw1G+VpiRHg=="
}
},
"is_incremental": false,