Skip to content

Commit a8c1534

Browse files
cilwernercilwerner
committed
copied metadata
1 parent 30c1168 commit a8c1534

15 files changed

+201
-17
lines changed

‎msal-javascript-conceptual/node/MIP-migration.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Migrate your Node.js application from ADAL to MSAL"
33
description: How to update your existing Node.js application to use the Microsoft Authentication Library (MSAL) for authentication and authorization instead of the Active Directory Authentication Library (ADAL).
4-
author: cilwerner
4+
author: EmLauber
55
manager: CelesteDG
66
ms.author: cwerner
77
ms.custom: has-adal-ref, devx-track-js
@@ -20,6 +20,13 @@ ms.topic: how-to
2020

2121
- Node version 10, 12, 14, 16 or 18. See the [note on version support](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node#node-version-support)
2222

23+
24+
## Migrate applications from ADAL Node to MSAL Node
25+
26+
For general remarks on differences between ADAL vs MSAL, as well as important dates and frequently asked questions, please refer to: [Migrate applications to the Microsoft Authentication Library (MSAL)](https://docs.microsoft.com/azure/active-directory/develop/msal-migration)
27+
28+
For specifics of migrating an app using ADAL Node to MSAL Node, including comparison between ADAL vs. MSAL public APIs, see the tutorial: [How to migrate a Node.js app from ADAL to MSAL](https://docs.microsoft.com/azure/active-directory/develop/msal-node-migration)
29+
2330
## Update app registration settings
2431

2532
When working with ADAL Node, you were likely using the **Azure AD v1.0 endpoint**. Apps migrating from ADAL to MSAL should switch to **Azure AD v2.0 endpoint**.

‎msal-javascript-conceptual/node/accounts.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,16 @@
11
---
2-
title: Overview
3-
description: Overview of the Microsoft Authentication Libraries for JavaScript
4-
services: active-directory
5-
author: Dickson-Mwendia
2+
title: "Migrate your Node.js application from ADAL to MSAL"
3+
description: How to update your existing Node.js application to use the Microsoft Authentication Library (MSAL) for authentication and authorization instead of the Active Directory Authentication Library (ADAL).
4+
author: EmLauber
65
manager: CelesteDG
7-
8-
ms.topic: reference
9-
ms.date: 11/29/2023
10-
ms.author: dmwendia
11-
ms.reviewer: emilylauber
6+
ms.author: emilylauber
7+
8+
ms.date: 04/26/2021
9+
ms.service: active-directory
10+
ms.subservice: develop
11+
ms.topic: conceptual
12+
ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
13+
#Customer intent: As an application developer, I want to learn how to change the code in my Node.js application from using ADAL as its authentication library to MSAL.
1214
---
1315

1416
# Accounts in MSAL Node
@@ -102,7 +104,7 @@ async function getResource() {
102104
account: account,
103105
scopes: scopes,
104106
};
105-
// Acquire Token Silently to be used in Resource API calll
107+
// Acquire Token Silently to be used in Resource API call
106108
pca.acquireTokenSilent(silentRequest)
107109
.then((response) => {
108110
// Handle successful resource API response

‎msal-javascript-conceptual/node/brokering.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,18 @@
1+
---
2+
title: "Acquiring Device Bound Tokens"
3+
description: Learn how to acquire tokens from the native token broker.
4+
author: EmLauber
5+
manager: CelesteDG
6+
ms.author: emilylauber
7+
8+
ms.date: 04/26/2021
9+
ms.service: active-directory
10+
ms.subservice: develop
11+
ms.topic: conceptual
12+
ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
13+
#Customer intent:
14+
---
15+
116
# Acquiring Device Bound Tokens
217

318
MSAL Node supports acquiring tokens from the native token broker. When using the native broker refresh tokens are bound to the device on which they are acquired on and are not accessible by `msal-node` or the application. This provides a higher level of security that cannot be achieved by `msal-node` alone.
@@ -6,7 +21,7 @@ MSAL Node supports acquiring tokens from the native token broker. When using the
621

722
This feature is currently only supported on Windows.
823

9-
## Pre-requisites
24+
## Prerequisites
1025

1126
- Install `@azure/msal-node-extensions` as a dependency
1227
- Register the broker's redirectUri on your app registration: `ms-appx-web://Microsoft.AAD.BrokerPlugin/<your-client-id>`, replacing `<your-client-id>` with your clientId.

‎msal-javascript-conceptual/node/caching.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,18 @@
1+
---
2+
title: "Acquiring Device Bound Tokens"
3+
description: Learn how to acquire tokens from the native token broker.
4+
author: EmLauber
5+
manager: CelesteDG
6+
ms.author: emilylauber
7+
8+
ms.date: 04/26/2021
9+
ms.service: active-directory
10+
ms.subservice: develop
11+
ms.topic: conceptual
12+
ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
13+
#Customer intent:
14+
---
15+
116
# Token caching in MSAL Node
217

318
When MSAL Node acquires a token, it caches it in memory for future usage. MSAL Node manages the token lifetime and refreshing for you. APIs like `acquireTokenSilent()` retrieves access tokens from the cache for a given account:

‎msal-javascript-conceptual/node/certificate-credentials.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,18 @@
1+
---
2+
title: "Acquiring Device Bound Tokens"
3+
description: Learn how to acquire tokens from the native token broker.
4+
author: EmLauber
5+
manager: CelesteDG
6+
ms.author: emilylauber
7+
8+
ms.date: 04/26/2021
9+
ms.service: active-directory
10+
ms.subservice: develop
11+
ms.topic: conceptual
12+
ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
13+
#Customer intent:
14+
---
15+
116
# Using certificate credentials with MSAL Node
217

318
> :warning: Before you start here, make sure you understand [Initialize confidential client applications](./initialize-confidential-client-application.md).

‎msal-javascript-conceptual/node/configuration.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,18 @@
1+
---
2+
title: "Acquiring Device Bound Tokens"
3+
description: Learn how to acquire tokens from the native token broker.
4+
author: EmLauber
5+
manager: CelesteDG
6+
ms.author: emilylauber
7+
8+
ms.date: 04/26/2021
9+
ms.service: active-directory
10+
ms.subservice: develop
11+
ms.topic: conceptual
12+
ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
13+
#Customer intent:
14+
---
15+
116
# Configuration Options
217

318
Before you start here, make sure you understand how to [initialize an app object](./initialize-public-client-application.md).

‎msal-javascript-conceptual/node/faq.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,18 @@
1+
---
2+
title: "Acquiring Device Bound Tokens"
3+
description: Learn how to acquire tokens from the native token broker.
4+
author: EmLauber
5+
manager: CelesteDG
6+
ms.author: emilylauber
7+
8+
ms.date: 04/26/2021
9+
ms.service: active-directory
10+
ms.subservice: develop
11+
ms.topic: conceptual
12+
ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
13+
#Customer intent:
14+
---
15+
116
# FAQs
217

318
## General

‎msal-javascript-conceptual/node/initialize-confidential-client-application.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,18 @@
1+
---
2+
title: "Acquiring Device Bound Tokens"
3+
description: Learn how to acquire tokens from the native token broker.
4+
author: EmLauber
5+
manager: CelesteDG
6+
ms.author: emilylauber
7+
8+
ms.date: 04/26/2021
9+
ms.service: active-directory
10+
ms.subservice: develop
11+
ms.topic: conceptual
12+
ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
13+
#Customer intent:
14+
---
15+
116
# Initialization of MSAL
217

318
Before you get started, please ensure you have completed all the [prerequisites](../README.md#prerequisites).

‎msal-javascript-conceptual/node/initialize-public-client-application.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,18 @@
1+
---
2+
title: "Acquiring Device Bound Tokens"
3+
description: Learn how to acquire tokens from the native token broker.
4+
author: EmLauber
5+
manager: CelesteDG
6+
ms.author: emilylauber
7+
8+
ms.date: 04/26/2021
9+
ms.service: active-directory
10+
ms.subservice: develop
11+
ms.topic: conceptual
12+
ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
13+
#Customer intent:
14+
---
15+
116
# Initialization of MSAL
217

318
Before you get started, please ensure you have completed all the [prerequisites](../README.md#prerequisites).

‎msal-javascript-conceptual/node/key-vault-managed-identity.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,18 @@
1+
---
2+
title: "Acquiring Device Bound Tokens"
3+
description: Learn how to acquire tokens from the native token broker.
4+
author: EmLauber
5+
manager: CelesteDG
6+
ms.author: emilylauber
7+
8+
ms.date: 04/26/2021
9+
ms.service: active-directory
10+
ms.subservice: develop
11+
ms.topic: conceptual
12+
ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
13+
#Customer intent:
14+
---
15+
116
# Securing MSAL Node app credentials with Azure Key Vault and Azure Managed Identity
217

318
> :warning: Before you start here, make sure you understand [Using certificate credentials with MSAL Node](./certificate-credentials.md).

0 commit comments

Comments
 (0)