Skip to content

Commit 038caee

Browse files
Merge pull request #238461 from FaithOmbongi/docs-editor/custom-extension-overview-1684311115
Update custom authentication extensions references
2 parents 65456b5 + efec836 commit 038caee

File tree

5 files changed

+55
-50
lines changed

5 files changed

+55
-50
lines changed

articles/active-directory/develop/custom-claims-provider-overview.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,12 +19,13 @@ ms.custom: aaddev
1919

2020
# Custom claims provider (preview)
2121

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.
2424

2525
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.
2626

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:
28+
2829
> [!VIDEO https://www.youtube.com/embed/1tPA7B9ztz0]
2930
3031
Use a custom claims provider for the following scenarios:
@@ -34,7 +35,7 @@ Use a custom claims provider for the following scenarios:
3435

3536
## Token issuance start event listener
3637

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.
3839

3940
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.
4041

@@ -43,3 +44,5 @@ For an example using a custom claims provider with the **token issuance start**
4344
- Learn how to [create and register a custom claims provider](custom-extension-get-started.md) with a sample Open ID Connect application.
4445
- 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.
4546
- Learn more about custom claims providers with the [custom claims provider reference](custom-claims-provider-reference.md) article.
47+
48+

articles/active-directory/develop/custom-extension-configure-saml-app.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ This article describes how to configure a SAML application to receive tokens wit
2626
Before configuring a SAML application to receive tokens with external claims, first follow these sections:
2727

2828
- [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)
3030

3131
## Configure a SAML application that receives enriched tokens
3232

@@ -70,7 +70,7 @@ Attributes that return by your custom claims provider API aren't automatically i
7070

7171
1. Select on **Configure** for **Custom claims provider**.
7272

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**.
7474

7575
1. Select **Add new claim** to add a new claim.
7676

0 commit comments

Comments
 (0)