You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/develop/custom-claims-provider-overview.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,12 +19,13 @@ ms.custom: aaddev
19
19
20
20
# Custom claims provider (preview)
21
21
22
-
This article provides an overview to the Azure Active Directory (Azure AD) custom claims provider.
23
-
When a user authenticates to an application, a custom claims provider can be used to add claims into the token. A custom claims provider is made up of a custom extension that calls an external REST API, to fetch claims from external systems. A custom claims provider can be assigned to one or many applications in your directory.
22
+
This article provides an overview to the Azure Active Directory (Azure AD) custom claims provider.
23
+
When a user authenticates to an application, a custom claims provider can be used to add claims into the token. A custom claims provider is made up of a custom authentication extension that calls an external REST API, to fetch claims from external systems. A custom claims provider can be assigned to one or many applications in your directory.
24
24
25
25
Key data about a user is often stored in systems external to Azure AD. For example, secondary email, billing tier, or sensitive information. Some applications may rely on these attributes for the application to function as designed. For example, the application may block access to certain features based on a claim in the token.
26
26
27
-
The following short video provides an excellent overview of the Azure AD custom extensions and custom claims providers:
27
+
The following short video provides an excellent overview of the Azure AD custom authentication extensions and custom claims providers:
Use a custom claims provider for the following scenarios:
@@ -34,7 +35,7 @@ Use a custom claims provider for the following scenarios:
34
35
35
36
## Token issuance start event listener
36
37
37
-
An event listener is a procedure that waits for an event to occur. The custom extension uses the **token issuance start** event listener. The event is triggered when a token is about to be issued to your application. When the event is triggered the custom extension REST API is called to fetch attributes from external systems.
38
+
An event listener is a procedure that waits for an event to occur. The custom authentication extension uses the **token issuance start** event listener. The event is triggered when a token is about to be issued to your application. When the event is triggered the custom authentication extension REST API is called to fetch attributes from external systems.
38
39
39
40
For an example using a custom claims provider with the **token issuance start** event listener, check out the [get started with custom claims providers](custom-extension-get-started.md) article.
40
41
@@ -43,3 +44,5 @@ For an example using a custom claims provider with the **token issuance start**
43
44
- Learn how to [create and register a custom claims provider](custom-extension-get-started.md) with a sample Open ID Connect application.
44
45
- If you already have a custom claims provider registered, you can configure a [SAML application](custom-extension-configure-saml-app.md) to receive tokens with claims sourced from an external store.
45
46
- Learn more about custom claims providers with the [custom claims provider reference](custom-claims-provider-reference.md) article.
Copy file name to clipboardExpand all lines: articles/active-directory/develop/custom-extension-configure-saml-app.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ This article describes how to configure a SAML application to receive tokens wit
26
26
Before configuring a SAML application to receive tokens with external claims, first follow these sections:
27
27
28
28
-[Create a custom claims provider API](custom-extension-get-started.md#step-1-create-an-azure-function-app)
29
-
-[Register a custom claims extension](custom-extension-get-started.md#step-2-register-a-custom-extension)
29
+
-[Register a custom claims extension](custom-extension-get-started.md#step-2-register-a-custom-authentication-extension)
30
30
31
31
## Configure a SAML application that receives enriched tokens
32
32
@@ -70,7 +70,7 @@ Attributes that return by your custom claims provider API aren't automatically i
70
70
71
71
1. Select on **Configure** for **Custom claims provider**.
72
72
73
-
1. Select the custom extension you [registered previously](custom-extension-get-started.md#step-2-register-a-custom-extension) in the **Custom claims provider** dropdown. Select **Save**.
73
+
1. Select the custom authentication extension you [registered previously](custom-extension-get-started.md#step-2-register-a-custom-authentication-extension) in the **Custom claims provider** dropdown. Select **Save**.
0 commit comments