Question

you are developing an azure app service web app. the app will use the microsoft authentication library for javascript (msal.js). you register the web app with the microsoft identity platform by using the azure portal. you need to configure the web app to receive the security tokens. the web app must process custom claims in the security tokens issued by azure active directory (azure ad). which value should you configure?

Answer 1

To configure the web app to receive security tokens and process custom claims, you need to configure the Callback URL, App ID URI, and Reply URLs in the Azure portal.

Step-by-step explanation:

In order to configure the web app to receive security tokens and process custom claims in the security tokens issued by Azure Active Directory (Azure AD), you should configure the Callback URL in the Azure portal. The Callback URL is the endpoint in your web app that will handle the authentication response and receive the security tokens.

Additionally, you need to configure the App ID URI in the Azure portal. The App ID URI represents the unique identifier for your web app and should match the value used in the MSAL.js code to validate the security tokens.

Finally, you should configure the Reply URLs in the Azure portal. Reply URLs specify the locations where Azure AD should redirect the users after they have authenticated successfully. Make sure to add all the URLs that your web app uses.

Answer 2

To configure the Azure App Service web app to receive security tokens that process custom claims, you must set the 'scope' in the token request to include the required permissions defined in Azure AD.

Step-by-step explanation:

The value you should configure to receive the security tokens which allows the web app to process custom claims is the scope in the token request. To ensure that your Azure App Service web app properly receives and processes custom claims within the security tokens issued by Azure Active Directory (Azure AD), you need to specify the desired permissions as scopes in your request to Azure AD. These permissions are defined during the app registration process in the Microsoft identity platform. You then utilize MSAL.js to acquire tokens that include these scopes, and hence, the associated claims you wish to process within your application.