Skip to content

Commit 17e5e35

Browse files
committed
refreshing certs and secrets
1 parent c6f3f37 commit 17e5e35

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed
85.3 KB
Loading

articles/active-directory/develop/quickstart-register-app.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: develop
1010
ms.topic: quickstart
1111
ms.workload: identity
12-
ms.date: 06/14/2021
12+
ms.date: 10/27/2021
1313
ms.author: marsma
1414
ms.custom: aaddev, identityplatformtop40, contperf-fy21q1, contperf-fy21q2, contperf-fy21q4
1515
# 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.
@@ -116,7 +116,7 @@ You can add both certificates and client secrets (a string) as credentials to yo
116116
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).
117117

118118
1. In the Azure portal, in **App registrations**, select your application.
119-
1. Select **Certificates & secrets** > **Upload certificate**.
119+
1. Select **Certificates & secrets** > **Certificates** > **Upload certificate**.
120120
1. Select the file you want to upload. It must be one of the following file types: _.cer_, _.pem_, _.crt_.
121121
1. Select **Add**.
122122

@@ -127,7 +127,7 @@ Sometimes called an _application password_, a client secret is a string value yo
127127
Client secrets are considered less secure than certificate credentials. Application developers sometimes use client secrets during local app development because of their ease of use. However, you should use certificate credentials for any application you have running in production.
128128

129129
1. In the Azure portal, in **App registrations**, select your application.
130-
1. Select **Certificates & secrets** > **New client secret**.
130+
1. Select **Certificates & secrets** > **Client secrets** > **New client secret**.
131131
1. Add a description for your client secret.
132132
1. Select an expiration for the secret or specify a custom lifetime.
133133
- Client secret lifetime is limited to two years (24 months) or less. You can't specify a custom lifetime longer than 24 months.

0 commit comments

Comments
 (0)