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
#Customer intent: As developer, I want to know how to register my application with the Microsoft identity platform so that the security token service can issue ID and/or access tokens to client applications that request them.
Copy file name to clipboardExpand all lines: includes/active-directory-develop-quickstart-register-app.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,16 +5,16 @@ Get started with the Microsoft identity platform by registering an application i
5
5
The Microsoft identity platform performs identity and access management (IAM) only for registered applications. Whether it's a client application like a web or mobile app, or it's a web API that backs a client app, registering it establishes a trust relationship between your application and the identity provider, the Microsoft identity platform.
6
6
7
7
> [!TIP]
8
-
> To register an application for Azure AD B2C, follow the steps in [Tutorial: Register a web application in Azure AD B2C](../../active-directory-b2c/tutorial-register-applications.md).
8
+
> To register an application for Azure AD B2C, follow the steps in [Tutorial: Register a web application in Azure AD B2C](../articles/active-directory-b2c/tutorial-register-applications.md).
9
9
10
10
## Prerequisites
11
11
12
12
- An Azure account that has an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
13
13
- The Azure account must have permission to manage applications in Azure Active Directory (Azure AD). Any of the following Azure AD roles include the required permissions:
- Completion of the [Set up a tenant](..//articles/active-directory/develop/quickstart-create-new-tenant.md) quickstart.
18
18
19
19
## Register an application
20
20
@@ -23,7 +23,7 @@ Registering your application establishes a trust relationship between your app a
23
23
Follow these steps to create the app registration:
24
24
25
25
1. Sign in to the <ahref="https://portal.azure.com/"target="_blank">Azure portal</a>.
26
-
1. If you have access to multiple tenants, use the **Directories + subscriptions** filter :::image type="icon" source="./media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
26
+
1. If you have access to multiple tenants, use the **Directories + subscriptions** filter :::image type="icon" source="../articles/active-directory/develop/media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
27
27
1. Search for and select **Azure Active Directory**.
28
28
1. Under **Manage**, select **App registrations** > **New registration**.
29
29
1. Enter a display **Name** for your application. Users of your application might see the display name when they use the app, for example during sign-in.
@@ -40,7 +40,7 @@ Follow these steps to create the app registration:
40
40
1. Don't enter anything for **Redirect URI (optional)**. You'll configure a redirect URI in the next section.
41
41
1. Select **Register** to complete the initial app registration.
42
42
43
-
:::image type="content" source="media/quickstart-register-app/portal-02-app-reg-01.png" alt-text="Screenshot of the Azure portal in a web browser, showing the Register an application pane.":::
43
+
:::image type="content" source="../articles/active-directory/develop/media/quickstart-register-app/portal-02-app-reg-01.png" alt-text="Screenshot of the Azure portal in a web browser, showing the Register an application pane.":::
44
44
45
45
When registration finishes, the Azure portal displays the app registration's **Overview** pane. You see the **Application (client) ID**. Also called the _client ID_, this value uniquely identifies your application in the Microsoft identity platform.
46
46
@@ -49,7 +49,7 @@ When registration finishes, the Azure portal displays the app registration's **O
49
49
50
50
Your application's code, or more typically an authentication library used in your application, also uses the client ID. The ID is used as part of validating the security tokens it receives from the identity platform.
51
51
52
-
:::image type="content" source="media/quickstart-register-app/portal-03-app-reg-02.png" alt-text="Screenshot of the Azure portal in a web browser, showing an app registration's Overview pane.":::
52
+
:::image type="content" source="../articles/active-directory/develop/media/quickstart-register-app/portal-03-app-reg-02.png" alt-text="Screenshot of the Azure portal in a web browser, showing an app registration's Overview pane.":::
53
53
54
54
## Add a redirect URI
55
55
@@ -70,7 +70,7 @@ To configure application settings based on the platform or device you're targeti
70
70
1. Under **Platform configurations**, select **Add a platform**.
71
71
1. Under **Configure platforms**, select the tile for your application type (platform) to configure its settings.
72
72
73
-
:::image type="content" source="media/quickstart-register-app/portal-04-app-reg-03-platform-config.png" alt-text="Screenshot of the platform configuration pane in the Azure portal." border="false":::
73
+
:::image type="content" source="../articles/active-directory/develop/media/quickstart-register-app/portal-04-app-reg-03-platform-config.png" alt-text="Screenshot of the platform configuration pane in the Azure portal." border="false":::
@@ -84,19 +84,19 @@ To configure application settings based on the platform or device you're targeti
84
84
85
85
### Redirect URI restrictions
86
86
87
-
There are some restrictions on the format of the redirect URIs you add to an app registration. For details about these restrictions, see [Redirect URI (reply URL) restrictions and limitations](reply-url.md).
87
+
There are some restrictions on the format of the redirect URIs you add to an app registration. For details about these restrictions, see [Redirect URI (reply URL) restrictions and limitations](../articles/active-directory/develop/reply-url.md).
88
88
89
89
## Add credentials
90
90
91
-
Credentials are used by [confidential client applications](msal-client-applications.md) that access a web API. Examples of confidential clients are web apps, other web APIs, or service-type and daemon-type applications. Credentials allow your application to authenticate as itself, requiring no interaction from a user at runtime.
91
+
Credentials are used by [confidential client applications](../articles/active-directory/develop/msal-client-applications.md) that access a web API. Examples of confidential clients are web apps, other web APIs, or service-type and daemon-type applications. Credentials allow your application to authenticate as itself, requiring no interaction from a user at runtime.
92
92
93
93
You can add both certificates and client secrets (a string) as credentials to your confidential client app registration.
94
94
95
-
:::image type="content" source="media/quickstart-register-app/portal-05-app-reg-04-credentials.png" alt-text="Screenshot of the Azure portal, showing the Certificates and secrets pane in an app registration.":::
95
+
:::image type="content" source="../articles/active-directory/develop/media/quickstart-register-app/portal-05-app-reg-04-credentials.png" alt-text="Screenshot of the Azure portal, showing the Certificates and secrets pane in an app registration.":::
96
96
97
97
### Add a certificate
98
98
99
-
Sometimes called a _public key_, a certificate is the recommended credential type because they're considered more secure than client secrets. For more information about using a certificate as an authentication method in your application, see [Microsoft identity platform application authentication certificate credentials](active-directory-certificate-credentials.md).
99
+
Sometimes called a _public key_, a certificate is the recommended credential type because they're considered more secure than client secrets. For more information about using a certificate as an authentication method in your application, see [Microsoft identity platform application authentication certificate credentials](../articles/active-directory/develop/active-directory-certificate-credentials.md).
100
100
101
101
1. In the Azure portal, in **App registrations**, select your application.
@@ -118,12 +118,12 @@ Client secrets are considered less secure than certificate credentials. Applicat
118
118
1. Select **Add**.
119
119
1._Record the secret's value_ for use in your client application code. This secret value is _never displayed again_ after you leave this page.
120
120
121
-
For application security recommendations, see [Microsoft identity platform best practices and recommendations](identity-platform-integration-checklist.md#security).
121
+
For application security recommendations, see [Microsoft identity platform best practices and recommendations](../articles/active-directory/develop/identity-platform-integration-checklist.md#security).
122
122
123
123
124
124
### Add a federated credential
125
125
126
-
Federated identity credentials are a type of credential that allows workloads, such as GitHub Actions, workloads running on Kubernetes, or workloads running in compute platforms outside of Azure access Azure AD protected resources without needing to manage secrets using [workload identity federation](workload-identity-federation.md).
126
+
Federated identity credentials are a type of credential that allows workloads, such as GitHub Actions, workloads running on Kubernetes, or workloads running in compute platforms outside of Azure access Azure AD protected resources without needing to manage secrets using [workload identity federation](../articles/active-directory/develop/workload-identity-federation.md).
127
127
128
128
To add a federated credential, follow these steps:
129
129
@@ -132,9 +132,9 @@ To add a federated credential, follow these steps:
132
132
1. In the **Federated credential scenario** drop-down box, select one of the supported scenarios, and follow the corresponding guidance to complete the configuration.
133
133
134
134
-**Customer managed keys** for encrypt data in your tenant using Azure Key Vault in another tenant.
135
-
-**GitHub actions deploying Azure resources** to [configure a GitHub workflow](workload-identity-federation-create-trust.md#github-actions) to get tokens for your application and deploy assets to Azure.
136
-
-**Kubernetes accessing Azure resources** to configure a [Kubernetes service account](workload-identity-federation-create-trust.md#kubernetes) to get tokens for your application and access Azure resources.
137
-
-**Other issuer** to configure an identity managed by an external [OpenID Connect provider](workload-identity-federation-create-trust.md#other-identity-providers) to get tokens for your application and access Azure resources.
135
+
-**GitHub actions deploying Azure resources** to [configure a GitHub workflow](../articles/active-directory/develop/workload-identity-federation-create-trust.md#github-actions) to get tokens for your application and deploy assets to Azure.
136
+
-**Kubernetes accessing Azure resources** to configure a [Kubernetes service account](../articles/active-directory/develop/workload-identity-federation-create-trust.md#kubernetes) to get tokens for your application and access Azure resources.
137
+
-**Other issuer** to configure an identity managed by an external [OpenID Connect provider](../articles/active-directory/develop/workload-identity-federation-create-trust.md#other-identity-providers) to get tokens for your application and access Azure resources.
138
138
139
139
140
-
For more information, how to get an access token with a federated credential, check out the [Microsoft identity platform and the OAuth 2.0 client credentials flow](v2-oauth2-client-creds-grant-flow.md#third-case-access-token-request-with-a-federated-credential) article.
140
+
For more information, how to get an access token with a federated credential, check out the [Microsoft identity platform and the OAuth 2.0 client credentials flow](../articles/active-directory/develop/v2-oauth2-client-creds-grant-flow.md#third-case-access-token-request-with-a-federated-credential) article.
0 commit comments