updated metadata

cilwerner · cilwerner · commit 4487fd97aed0 · 2023-12-01T15:41:40.000Z
diff --git a/msal-javascript-conceptual/node/MIP-caching.md b/msal-javascript-conceptual/node/MIP-caching.md
@@ -1,5 +1,5 @@
 ---
-title: "Learn about Microsoft Authentication Extensions for Node"
+title: "Microsoft Authentication Extensions for Node"
 description: The Microsoft Authentication Extensions for Node enables application developers to perform cross-platform token cache serialization and persistence. It gives extra support to the Microsoft Authentication Library for Node (MSAL Node).
 author: henrymbuguakiarie
 manager: CelesteDG
diff --git a/msal-javascript-conceptual/node/MIP-initialize-client-apps-v2-v1.md b/msal-javascript-conceptual/node/MIP-initialize-client-apps-v2-v1.md
@@ -1,5 +1,5 @@
 ---
-title: Initialize MSAL.js client apps
+title: Initialize client applications using MSAL.js
 description: Learn about initializing client applications using the Microsoft Authentication Library for JavaScript (MSAL.js).
 author: OwenRichards1
 manager: CelesteDG
diff --git a/msal-javascript-conceptual/node/MIP-migration.md b/msal-javascript-conceptual/node/MIP-migration.md
@@ -12,7 +12,7 @@ ms.topic: how-to
 #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.
 ---
 
-# How to migrate a Node.js app from ADAL to MSAL
+# Migrate your Node.js application from ADAL to MSAL
 
 [Microsoft Authentication Library for Node](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node) (MSAL Node) is now the recommended SDK for enabling authentication and authorization for your applications registered on the Microsoft identity platform. This article covers the important steps you need to go through in order to migrate your apps from Active Directory Authentication Library for Node (ADAL Node) to MSAL Node.
 
diff --git a/msal-javascript-conceptual/node/accounts.md b/msal-javascript-conceptual/node/accounts.md
@@ -1,6 +1,6 @@
 ---
-title: "Migrate your Node.js application from ADAL to MSAL"
-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).
+title: Accounts in MSAL Node
+description: Learn how to use the different APIs in MSAL Node to access cached accounts.
 author: EmLauber
 manager: CelesteDG
 ms.author: emilylauber
@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
 ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
-#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.
+#Customer intent: As a developer, I want to learn how to use the different APIs in MSAL Node to access cached accounts.
 ---
 
 # Accounts in MSAL Node
diff --git a/msal-javascript-conceptual/node/brokering.md b/msal-javascript-conceptual/node/brokering.md
@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
 ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
-#Customer intent: 
+#Customer intent: As a developer, I want to learn how to acquire tokens from the native token broker.
 ---
 
 # Acquiring Device Bound Tokens
diff --git a/msal-javascript-conceptual/node/caching.md b/msal-javascript-conceptual/node/caching.md
@@ -1,6 +1,6 @@
 ---
-title: "Acquiring Device Bound Tokens"
-description: Learn how to acquire tokens from the native token broker.
+title: Token caching in MSAL Node
+description: Learn how to effectively cache tokens in MSAL Node, and use client secrets securely,
 author: EmLauber
 manager: CelesteDG
 ms.author: emilylauber
@@ -9,7 +9,7 @@ ms.date: 04/26/2021
 ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
-ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
+ms.reviewer: dmwendia, cwerner, owenrichards, kengaderdus
 #Customer intent: 
 ---
 
diff --git a/msal-javascript-conceptual/node/certificate-credentials.md b/msal-javascript-conceptual/node/certificate-credentials.md
@@ -1,6 +1,6 @@
 ---
-title: "Acquiring Device Bound Tokens"
-description: Learn how to acquire tokens from the native token broker.
+title: Using certificate credentials with MSAL Node
+description: Learn how to use certificate credentials with MSAL Node. Create, register and initialize certificates, and use them securely.
 author: EmLauber
 manager: CelesteDG
 ms.author: emilylauber
diff --git a/msal-javascript-conceptual/node/configuration.md b/msal-javascript-conceptual/node/configuration.md
@@ -1,5 +1,5 @@
 ---
-title: "Acquiring Device Bound Tokens"
+title: Configure MSAL Node
 description: Learn how to acquire tokens from the native token broker.
 author: EmLauber
 manager: CelesteDG
@@ -13,7 +13,7 @@ ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
 #Customer intent: 
 ---
 
-# Configuration Options
+# Configure MSAL Node
 
 Before you start here, make sure you understand how to [initialize an app object](./initialize-public-client-application.md).
 
diff --git a/msal-javascript-conceptual/node/faq.md b/msal-javascript-conceptual/node/faq.md
@@ -1,6 +1,6 @@
 ---
-title: "Acquiring Device Bound Tokens"
-description: Learn how to acquire tokens from the native token broker.
+title: Frequently asked questions about MSAL Node
+description: Learn about the most frequently asked questions about MSAL Node.
 author: EmLauber
 manager: CelesteDG
 ms.author: emilylauber
@@ -13,64 +13,79 @@ ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
 #Customer intent: 
 ---
 
-# FAQs
+# Frequently asked questions about MSAL Node
 
 ## General
 
 ### When is MSAL Node used?
+
 MSAL Node supports server based authentication for public/confidential apps. This is more applicable for server based authentication scenarios/Web APIs that need authentication. A full list of supported scenarios can be found [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node#scenarios-supported) and supported flows are listed [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node#oauth20-grant-types-supported)
 
 ### What is the status of ADAL Node? Is a migration guide available?
+
 ADAL Node is currently in maintanence and we advise all users to move to MSAL Node as possible. MSAL Node is designed to completely replace ADAL node. For those looking to migrate from ADAL to MSAL we have provided a [Migration Document](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-node/docs/migration.md) to help in the migration. Please note that all apps may not have a smooth migration as this is complete overhaul of the old functionality.
 
 ### What are the services supported?
+
 MSAL Node supports AAD, MSA, ADFS and B2C. Our samples demonstrate the usage [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-node-samples/standalone-samples). MSAL Node also supports [single and multi tenanted apps](https://docs.microsoft.com/azure/active-directory/develop/single-and-multi-tenant-apps).
 
 Note: ADFS is currently supported, a standalone sample is not yet published. Please checkout this space for an update soon.
 
 ### What is a Public App or a Confidential App? What do I need to know during app registration?
+
 Please find this in the [MSAL basics](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node#msal-basics)
 
 ## What does authority string default to if I provide "authority" and "azureCloudOptions"?
 
 If the developer provides `azureCloudOptions`, MSAL.js will overwrite any value provided in the `authority`. MSAL.js will also give preference to the parameters provided in a `request` over `configuration`. Please note that if `azureCloudOptions` are set in the configuration, they will take precedence over `authority` in the `request`. If the developer needs to overwrite this, they need to set `azureCloudOptions` in the `request`.
 
 ### What will be the token lifetimes?
+
 * AAD: Please find the latest reference for AAD [here](https://docs.microsoft.com/azure/active-directory/develop/active-directory-configurable-token-lifetimes). Please note that few of the configurable features for specific token types are retired recently.
 * B2C: Please find the B2C token lifetime guidance [here](https://docs.microsoft.com/azure/active-directory-b2c/tokens-overview#configuration)
 
 ### How do I get the Refresh Token?
+
 MSAL Node does not expose refresh tokens for security reasons. Instead, we manage the refresh token through the cache and update it as required to fetch the corresponding Id Token and Access Token for the developer. Use the appropriate `acquireToken*` API to obtain access tokens, and MSAL will ensure they are renewed if necessary. If you have a refresh token acquired by other means, you can use the [acquireTokenByRefreshToken](https://azuread.github.io/microsoft-authentication-library-for-js/ref/classes/_azure_msal_node.confidentialclientapplication.html#acquiretokenbyrefreshtoken) API (see also: [Refresh Token sample](../../../samples/msal-node-samples/refresh-token/README.md)). More details on AAD tokens can be found [here](https://learn.microsoft.com/azure/active-directory/develop/security-tokens)
 
 ### Is Electron supported?
+
 Yes. Please refer to [MSAL Node samples](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-node-samples).
 
 ### Is interactive flow supported?
+
 Currently No. Authentication for MSAL Node using authorization code grant is a two legged flow, as detailed [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-common/docs/request.md). There are plans to provide a single API to achieve this, and invoke the browser on the user's behalf. However it is currently not supported.
 
 ### Are SPAs supported by MSAL Node?
+
 Please refer to [MSAL Browser](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-browser) for SPA based use cases. MSAL Node should be a choice for desktop apps, web apps, web APIs or server side authentication scenarios.
 
 ### What is MSAL Node extensions? What is a Cache Plugin?
+
 MSAL Node extensions is a support library for MSAL Node which offers secure mechanisms for client applications to perform cross-platform token cache serialization and persistence. Please find the usage, samples and more about this [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/extensions)
 
 ### Can the cache plugin provided in MSAL Node extensions be used in Electron applications?
+
 Yes, it can. In case you run into node version related issues, refer to this [note](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/extensions/docs/msal-node-extensions.md#note-for-electron-developers) that provides the steps to troubleshoot.
 
 ### What versions of Node.js are supported? How do I bypass the installation error if I want to use an active development Node.js version?
+
 MSAL Node officially supports even numbered stable LTS releases as documented [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node#node-version-support).
 
 If you want to work around this, please note:
 - **Yarn**: Pass the `--ignore-engines` flag to the `yarn` command.
 - **npm**: Add `engine-strict=false` to your .npmrc file.
 
 ### How do I implement self-service sign-up with MSAL Node?
+
 MSAL Node supports self-service sign-up in the auth code flow. Please see our docs [here](https://azuread.github.io/microsoft-authentication-library-for-js/ref/modules/_azure_msal_node.html#authorizationurlrequest) for supported prompt values in the request and their expected outcomes, and [here](http://aka.ms/s3u) for an overview of self-service sign-up and configuration changes that need to be made to your Azure tenant. Please note that that self-service sign-up is not available in B2C and test environments.
 
 ### Why doesn't my app function correctly when it's running behind a proxy?
+
 Developers can provide a `proxyUrl` string in the system config options as detailed [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-node/docs/configuration.md#system-config-options). Developers can also implement their own NetworkManager by instantiating an [INetworkModule](https://azuread.github.io/microsoft-authentication-library-for-js/ref/interfaces/_azure_msal_common.inetworkmodule.html) and building proxy support in it.
 
 ### How do I implement a custom http(s) agent in MSAL Node?
+
 Developers can use a custom http(s) agent by providing a `customAgentOptions` object in the system config options as detailed [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-node/docs/configuration.md#system-config-options). Developers can also implement their own NetworkManager by instantiating an [INetworkModule](https://azuread.github.io/microsoft-authentication-library-for-js/ref/interfaces/_azure_msal_common.inetworkmodule.html) and building custom http(s) agent support in it.
 
 ## B2C
diff --git a/msal-javascript-conceptual/node/initialize-confidential-client-application.md b/msal-javascript-conceptual/node/initialize-confidential-client-application.md
@@ -1,6 +1,6 @@
 ---
-title: "Acquiring Device Bound Tokens"
-description: Learn how to acquire tokens from the native token broker.
+title: Initialize the confidential client application object in MSAL Node 
+description: Learn how to initialize MSAL Node.
 author: EmLauber
 manager: CelesteDG
 ms.author: emilylauber
@@ -13,7 +13,7 @@ ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
 #Customer intent: 
 ---
 
-# Initialization of MSAL
+# Initialize the confidential client application object in MSAL Node 
 
 Before you get started, please ensure you have completed all the [prerequisites](../README.md#prerequisites).
 
diff --git a/msal-javascript-conceptual/node/initialize-public-client-application.md b/msal-javascript-conceptual/node/initialize-public-client-application.md
@@ -1,5 +1,5 @@
 ---
-title: "Acquiring Device Bound Tokens"
+title: Initialize the public client application object in MSAL Node 
 description: Learn how to acquire tokens from the native token broker.
 author: EmLauber
 manager: CelesteDG
@@ -13,7 +13,7 @@ ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
 #Customer intent: 
 ---
 
-# Initialization of MSAL
+# Initialize the public client application object in MSAL Node 
 
 Before you get started, please ensure you have completed all the [prerequisites](../README.md#prerequisites).
 
diff --git a/msal-javascript-conceptual/node/key-vault-managed-identity.md b/msal-javascript-conceptual/node/key-vault-managed-identity.md
@@ -1,5 +1,5 @@
 ---
-title: "Acquiring Device Bound Tokens"
+title: Securing MSAL Node app credentials with Azure Key Vault and Azure Managed Identity
 description: Learn how to acquire tokens from the native token broker.
 author: EmLauber
 manager: CelesteDG
diff --git a/msal-javascript-conceptual/node/performance.md b/msal-javascript-conceptual/node/performance.md
@@ -1,6 +1,6 @@
 ---
-title: "Acquiring Device Bound Tokens"
-description: Learn how to acquire tokens from the native token broker.
+title: Performance in MSAL Node
+description: Learn how to measure performance in MSAL Node.
 author: EmLauber
 manager: CelesteDG
 ms.author: emilylauber
diff --git a/msal-javascript-conceptual/node/regional-authorities.md b/msal-javascript-conceptual/node/regional-authorities.md
@@ -1,6 +1,6 @@
 ---
-title: "Acquiring Device Bound Tokens"
-description: Learn how to acquire tokens from the native token broker.
+title: Enabling regional authorities
+description: Learn how to enable regional authorities in MSAL Node.
 author: EmLauber
 manager: CelesteDG
 ms.author: emilylauber
diff --git a/msal-javascript-conceptual/node/request.md b/msal-javascript-conceptual/node/request.md
@@ -1,5 +1,5 @@
 ---
-title: "Acquiring Device Bound Tokens"
+title: "Acquiring tokens in MSAL Node"
 description: Learn how to acquire tokens from the native token broker.
 author: EmLauber
 manager: CelesteDG
@@ -13,13 +13,14 @@ ms.reviewer: dmwendia,cwerner, owenrichards, kengaderdus
 #Customer intent: 
 ---
 
-# Request
+# Acquire tokens in MSAL Node
 
 Since MSAL Node supports various authorization code grants, there is support for different public APIs per grant and the corresponding request.
 
 ## Authorization Code Flow
 
 ### Public APIs
+
 - [getAuthCodeUrl()](https://azuread.github.io/microsoft-authentication-library-for-js/ref/msal-node/classes/_src_client_publicclientapplication_.publicclientapplication.html#getauthcodeurl): This API is the first leg of the `authorization code grant` for MSAL Node. The request is of the type [AuthorizationUrlRequest](https://azuread.github.io/microsoft-authentication-library-for-js/ref/msal-common/modules/_src_request_authorizationurlrequest_.html).
 The application is sent a URL that can be used to generate an `authorization code`. This URL can be opened in a browser of choice, where the user can input their credentials, and will be redirected back to the `redirectUri` (registered during the [app registration](https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-desktop-app-registration)) with an `authorization code`. The `authorization code` can now be redeemed for a `token` with the following step. Note that if authorization code flow is being done for a public client application, [PKCE](https://tools.ietf.org/html/rfc7636) is recommended.
 
@@ -54,6 +55,7 @@ The application is sent a URL that can be used to generate an `authorization cod
 ## Device Code Flow
 
 ### Public APIs
+
 - [acquireTokenByDeviceCode()](https://azuread.github.io/microsoft-authentication-library-for-js/ref/msal-node/classes/_src_client_publicclientapplication_.publicclientapplication.html#acquiretokenbydevicecode): This API lets the application acquire a token with Device Code grant. The request is of the type [DeviceCodeRequest](https://azuread.github.io/microsoft-authentication-library-for-js/ref/msal-common/modules/_src_request_devicecoderequest_.html). This API acquires a `token` from the authority using OAuth2.0 device code flow. This flow is designed for devices that do not have access to a browser or have input constraints. The authorization server issues a DeviceCode object with a verification code, an end-user code, and the end-user verification URI. The DeviceCode object is provided through a callback, and the end-user should be instructed to use another device to navigate to the verification URI to input credentials. Since the client cannot receive incoming requests, it polls the authorization server repeatedly until the end-user completes input of credentials.
 
 ``` javascript
diff --git a/msal-javascript-conceptual/node/sni.md b/msal-javascript-conceptual/node/sni.md
@@ -1,5 +1,5 @@
 ---
-title: "Acquiring Device Bound Tokens"
+title: Implement SNI Authentication with MSAL Node
 description: Learn how to acquire tokens from the native token broker.
 author: EmLauber
 manager: CelesteDG
