lsm/openiddict-documentation
1
0
Fork 0
mirror of https://gitee.com/dcren/openiddict-documentation.git synced 2025-07-15 14:04:34 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update the documentation pages

Browse Source
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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
configuration/application-permissions.html
View File

@ -283,9 +283,8 @@ if (await manager.FindByClientIdAsync("console") is null)
options.IgnoreScopePermissions(); options.IgnoreScopePermissions();
}); });
</code></pre><h2 id="response-type-permissions">Response type permissions</h2> </code></pre><h2 id="response-type-permissions">Response type permissions</h2>
<p>-&gt; [!NOTE]</p> <p>-&gt; [!NOTE]
<blockquote><p>Response type permissions were introduced in OpenIddict 3.0.</p> -&gt; Response type permissions were introduced in OpenIddict 3.0.</p>
</blockquote>
<h3 id="definition-3">Definition</h3> <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> <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> <h3 id="supported-permissions-3">Supported permissions</h3>

46
guide/getting-started.html
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. // to replace the default OpenIddict entities.
options.UseOpenIddict(); options.UseOpenIddict();
}); });
</code></pre></li> </code></pre><p>-&gt; [!WARNING]
</ul> -&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>
<p>-&gt; [!WARNING]</p> -&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:
<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> -&gt;
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> -&gt; <code>csharp
<pre><code class="lang-csharp">services.AddOpenIddict() -&gt; services.AddOpenIddict()
.AddCore(options =&gt; -&gt; .AddCore(options =&gt;
{ -&gt; {
// Configure OpenIddict to use the default entities with a custom key type. -&gt; // Configure OpenIddict to use the default entities with a custom key type.
options.UseEntityFrameworkCore() -&gt; options.UseEntityFrameworkCore()
.UseDbContext&lt;ApplicationDbContext&gt;() -&gt; .UseDbContext&lt;ApplicationDbContext&gt;()
.ReplaceDefaultEntities&lt;Guid&gt;(); -&gt; .ReplaceDefaultEntities&lt;Guid&gt;();
}); -&gt; });
-&gt;
services.AddDbContext&lt;ApplicationDbContext&gt;(options =&gt; -&gt; services.AddDbContext&lt;ApplicationDbContext&gt;(options =&gt;
{ -&gt; {
// Configure the context to use Microsoft SQL Server. -&gt; // Configure the context to use Microsoft SQL Server.
options.UseSqlServer(configuration[&quot;Data:DefaultConnection:ConnectionString&quot;]); -&gt; options.UseSqlServer(configuration[&quot;Data:DefaultConnection:ConnectionString&quot;]);
-&gt;
options.UseOpenIddict&lt;Guid&gt;(); -&gt; options.UseOpenIddict&lt;Guid&gt;();
}); -&gt; });
</code></pre></blockquote> -&gt;</code></p>
<ul> </li>
<li><p><strong>Create your own authorization controller:</strong> <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. 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> Here&#39;s an example for the client credentials grant:</p>

4
manifest.json
View File

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