From d52dd13c07632789984d19e33aa96501455d18ab Mon Sep 17 00:00:00 2001 From: OpenIddict Bot <32257313+openiddict-bot@users.noreply.github.com> Date: Thu, 13 Sep 2018 12:49:08 +0000 Subject: [PATCH] Update the documentation pages --- configuration/application-permissions.html | 35 +++++++++++++++++++++- manifest.json | 10 +++---- 2 files changed, 39 insertions(+), 6 deletions(-) diff --git a/configuration/application-permissions.html b/configuration/application-permissions.html index ce5ef94..c700300 100644 --- a/configuration/application-permissions.html +++ b/configuration/application-permissions.html @@ -228,7 +228,40 @@ if (await manager.FindByClientIdAsync("console") == null)

Scope permissions limit the scopes (standard or custom) a client application is allowed to use.

The openid and offline_access scopes are special-cased by OpenIddict and don't require explicit permissions.

-

Example

+

Supported permissions

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ScopeConstant
addressOpenIddictConstants.Permissions.Scopes.Address
emailOpenIddictConstants.Permissions.Scopes.Email
phoneOpenIddictConstants.Permissions.Scopes.Phone
profileOpenIddictConstants.Permissions.Scopes.Profile
rolesOpenIddictConstants.Permissions.Scopes.Roles
+

To add a custom scope permission, you can use the following pattern:

+
OpenIddictConstants.Permissions.Prefixes.Scope + "custom_scope_name"
+

Example

In the following sample, the angular client is allowed to request the address, profile and marketing_api scopes: any other scope will result in an error being returned.

if (await manager.FindByClientIdAsync("angular") == null)
diff --git a/manifest.json b/manifest.json
index cb571fe..e73ae92 100644
--- a/manifest.json
+++ b/manifest.json
@@ -9,7 +9,7 @@
       "output": {
         ".html": {
           "relative_path": "configuration/application-permissions.html",
-          "hash": "bKUoTWvuQdArH/6SAvdCnw=="
+          "hash": "LOmSHldwDeJLrrKM8vU/xA=="
         }
       },
       "is_incremental": false,
@@ -232,18 +232,18 @@
           "details": "Processor RestApiDocumentProcessor cannot suppport incremental build because the processor doesn't implement ISupportIncrementalDocumentProcessor interface.",
           "incrementalPhase": "build"
         },
-        "TocDocumentProcessor": {
+        "ResourceDocumentProcessor": {
           "can_incremental": false,
-          "details": "Processor TocDocumentProcessor cannot suppport incremental build because the processor doesn't implement ISupportIncrementalDocumentProcessor interface.",
+          "details": "Processor ResourceDocumentProcessor cannot suppport incremental build because the processor doesn't implement ISupportIncrementalDocumentProcessor interface.",
           "incrementalPhase": "build"
         },
         "ConceptualDocumentProcessor": {
           "can_incremental": false,
           "incrementalPhase": "build"
         },
-        "ResourceDocumentProcessor": {
+        "TocDocumentProcessor": {
           "can_incremental": false,
-          "details": "Processor ResourceDocumentProcessor cannot suppport incremental build because the processor doesn't implement ISupportIncrementalDocumentProcessor interface.",
+          "details": "Processor TocDocumentProcessor cannot suppport incremental build because the processor doesn't implement ISupportIncrementalDocumentProcessor interface.",
           "incrementalPhase": "build"
         },
         "ManagedReferenceDocumentProcessor": {