Skip to content

Commit 2cb2a27

Browse files
node.js-console-app-portal-doc
1 parent 5360451 commit 2cb2a27

File tree

4 files changed

+24
-82
lines changed

4 files changed

+24
-82
lines changed

articles/active-directory/develop/quickstart-v2-java-daemon.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ author: mmacy
77
manager: CelesteDG
88
ms.service: active-directory
99
ms.subservice: develop
10-
ms.topic: quickstart
10+
ms.topic: portal
1111
ms.workload: identity
12-
ms.date: 01/22/2021
12+
ms.date: 01/10/2022
1313
ms.author: marsma
1414
ms.custom: aaddev, "scenarios:getting-started", "languages:Java", devx-track-java, mode-api
1515
#Customer intent: As an application developer, I want to learn how my Java app can get an access token and call an API that's protected by Microsoft identity platform endpoint using client credentials flow.

articles/active-directory/develop/quickstart-v2-netcore-daemon.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ author: jmprieur
77
manager: CelesteDG
88
ms.service: active-directory
99
ms.subservice: develop
10-
ms.topic: quickstart
10+
ms.topic: portal
1111
ms.workload: identity
12-
ms.date: 10/05/2020
12+
ms.date: 01/10/2022
1313
ms.author: jmprieur
1414
ms.reviewer: marsma
1515
ms.custom: devx-track-csharp, aaddev, identityplatformtop40, "scenarios:getting-started", "languages:aspnet-core", mode-api

articles/active-directory/develop/quickstart-v2-nodejs-console.md

Lines changed: 18 additions & 76 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ author: mmacy
77
manager: CelesteDG
88
ms.service: active-directory
99
ms.subservice: develop
10-
ms.topic: quickstart
11-
ms.date: 02/17/2021
10+
ms.topic: portal
11+
ms.date: 01/10/2022
1212
ms.author: marsma
1313
ms.custom: mode-api
1414
#Customer intent: As an application developer, I want to learn how my Node.js app can get an access token and call an API that is protected by a Microsoft identity platform endpoint using client credentials flow.
@@ -25,83 +25,33 @@ This quickstart uses the [Microsoft Authentication Library for Node.js (MSAL Nod
2525
* [Node.js](https://nodejs.org/en/download/)
2626
* [Visual Studio Code](https://code.visualstudio.com/download) or another code editor
2727

28-
> [!div renderon="docs"]
29-
> ## Register and download the sample application
30-
>
31-
> Follow the steps below to get started.
32-
>
33-
> [!div renderon="docs"]
34-
> #### Step 1: Register the application
35-
> To register your application and add the app's registration information to your solution manually, follow these steps:
36-
>
37-
> 1. Sign in to the <a href="https://portal.azure.com/" target="_blank">Azure portal</a>.
38-
> 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.
39-
> 1. Search for and select **Azure Active Directory**.
40-
> 1. Under **Manage**, select **App registrations** > **New registration**.
41-
> 1. Enter a **Name** for your application, for example `msal-node-cli`. Users of your app might see this name, and you can change it later.
42-
> 1. Select **Register**.
43-
> 1. Under **Manage**, select **Certificates & secrets**.
44-
> 1. Under **Client secrets**, select **New client secret**, enter a name, and then select **Add**. Record the secret value in a safe location for use in a later step.
45-
> 1. Under **Manage**, select **API Permissions** > **Add a permission**. Select **Microsoft Graph**.
46-
> 1. Select **Application permissions**.
47-
> 1. Under **User** node, select **User.Read.All**, then select **Add permissions**.
48-
49-
> [!div class="sxs-lookup" renderon="portal"]
50-
> ### Download and configure the sample app
51-
>
52-
> #### Step 1: Configure the application in Azure portal
53-
> For the code sample for this quickstart to work, you need to create a client secret, and add Graph API's **User.Read.All** application permission.
54-
> > [!div renderon="portal" id="makechanges" class="nextstepaction"]
55-
> > [Make these changes for me]()
56-
>
57-
> > [!div id="appconfigured" class="alert alert-info"]
58-
> > ![Already configured](media/quickstart-v2-netcore-daemon/green-check.png) Your application is configured with these attributes.
5928

60-
#### Step 2: Download the Node.js sample project
29+
### Download and configure the sample app
6130

62-
> [!div renderon="docs"]
63-
> [Download the code sample](https://github.com/azure-samples/ms-identity-javascript-nodejs-console/archive/main.zip)
31+
#### Step 1: Configure the application in Azure portal
32+
For the code sample for this quickstart to work, you need to create a client secret, and add Graph API's **User.Read.All** application permission.
33+
> [!div class="nextstepaction"]
34+
> [Make these changes for me]()
6435
65-
> [!div renderon="portal" id="autoupdate" class="sxs-lookup nextstepaction"]
36+
> [!div class="alert alert-info"]
37+
> ![Already configured](media/quickstart-v2-netcore-daemon/green-check.png) Your application is configured with these attributes.
38+
39+
#### Step 2: Download the Node.js sample project
40+
41+
> [!div class="sxs-lookup nextstepaction"]
6642
> [Download the code sample](https://github.com/azure-samples/ms-identity-javascript-nodejs-console/archive/main.zip)
6743
68-
> [!div class="sxs-lookup" renderon="portal"]
44+
> [!div class="sxs-lookup"]
6945
> > [!NOTE]
7046
> > `Enter_the_Supported_Account_Info_Here`
7147
72-
> [!div renderon="docs"]
73-
> #### Step 3: Configure the Node.js sample project
74-
>
75-
> 1. Extract the zip file to a local folder close to the root of the disk, for example, *C:/Azure-Samples*.
76-
> 1. Edit *.env* and replace the values of the fields `TENANT_ID`, `CLIENT_ID`, and `CLIENT_SECRET` with the following snippet:
77-
>
78-
> ```
79-
> "TENANT_ID": "Enter_the_Tenant_Id_Here",
80-
> "CLIENT_ID": "Enter_the_Application_Id_Here",
81-
> "CLIENT_SECRET": "Enter_the_Client_Secret_Here"
82-
> ```
83-
> Where:
84-
> - `Enter_the_Application_Id_Here` - is the **Application (client) ID** of the application you registered earlier. Find this ID on the app registration's **Overview** pane in the Azure portal.
85-
> - `Enter_the_Tenant_Id_Here` - replace this value with the **Tenant ID** or **Tenant name** (for example, contoso.microsoft.com). Find these values on the app registration's **Overview** pane in the Azure portal.
86-
> - `Enter_the_Client_Secret_Here` - replace this value with the client secret you created earlier. To generate a new key, use **Certificates & secrets** in the app registration settings in the Azure portal.
87-
>
88-
> > [!WARNING]
89-
> > Any plaintext secret in source code poses an increased security risk. This article uses a plaintext client secret for simplicity only. Use [certificate credentials](active-directory-certificate-credentials.md) instead of client secrets in your confidential client applications, especially those apps you intend to deploy to production.
90-
91-
> [!div class="sxs-lookup" renderon="portal"]
92-
> #### Step 3: Admin consent
93-
94-
> [!div renderon="docs"]
95-
> #### Step 4: Admin consent
48+
#### Step 3: Admin consent
9649

9750
If you try to run the application at this point, you'll receive *HTTP 403 - Forbidden* error: `Insufficient privileges to complete the operation`. This error happens because any *app-only permission* requires **admin consent**: a global administrator of your directory must give consent to your application. Select one of the options below depending on your role:
9851

9952
##### Global tenant administrator
10053

101-
> [!div renderon="docs"]
102-
> If you are a global tenant administrator, go to **API Permissions** page in the Azure portal's Application Registration and select **Grant admin consent for {Tenant Name}** (where {Tenant Name} is the name of your directory).
103-
104-
> [!div renderon="portal" class="sxs-lookup"]
54+
> [!div class="sxs-lookup"]
10555
> If you are a global administrator, go to **API Permissions** page select **Grant admin consent for Enter_the_Tenant_Name_Here**
10656
> > [!div id="apipermissionspage"]
10757
> > [Go to the API Permissions page]()
@@ -114,16 +64,8 @@ If you're a standard user of your tenant, then you need to ask a global administ
11464
https://login.microsoftonline.com/Enter_the_Tenant_Id_Here/adminconsent?client_id=Enter_the_Application_Id_Here
11565
```
11666

117-
> [!div renderon="docs"]
118-
>> Where:
119-
>> * `Enter_the_Tenant_Id_Here` - replace this value with the **Tenant Id** or **Tenant name** (for example, contoso.microsoft.com)
120-
>> * `Enter_the_Application_Id_Here` - is the **Application (client) ID** for the application you registered.
121-
122-
> [!div class="sxs-lookup" renderon="portal"]
123-
> #### Step 4: Run the application
124-
125-
> [!div renderon="docs"]
126-
> #### Step 5: Run the application
67+
> [!div class="sxs-lookup"]
68+
#### Step 4: Run the application
12769

12870
Locate the sample's root folder (where `package.json` resides) in a command prompt or console. You'll need to install the dependencies of this sample once:
12971

articles/active-directory/develop/quickstart-v2-python-daemon.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ author: jmprieur
77
manager: CelesteDG
88
ms.service: active-directory
99
ms.subservice: develop
10-
ms.topic: quickstart
10+
ms.topic: portal
1111
ms.workload: identity
12-
ms.date: 10/22/2019
12+
ms.date: 01/10/2022
1313
ms.author: jmprieur
1414
ms.custom: aaddev, identityplatformtop40, devx-track-python, "scenarios:getting-started", "languages:Python", mode-api
1515
#Customer intent: As an application developer, I want to learn how my Python app can get an access token and call an API that's protected by the Microsoft identity platform using client credentials flow.

0 commit comments

Comments
 (0)