msal

问题 I want to set up some end to end tests for my Angular application, which requires the use of the MSAL library to authenticate with some downstream services. When I try to run my e2e tests locally, the MSAL library is forcing me to authenticate with a username/password. This is a problem because our CI/CD e2e testing should not have any human-intervention; thus I am looking for a way to either bypass the MSAL authentication or set up a service-account to login. Unfortunately there is not a lot

问题 ADAL.js and AAD v1 works to access Azure DevOps using delegated user_impersonation scope. I used the same AAD Application Id with delegated permissions to generate access tokens using MSAL.js. The tokens were created successfully, but the access token does not work to access Azure DevOps. The only meaningful difference in the decoded JWT token is that the "aud" claims are different. In ADAL/v1, the aud is the application id of Azure DevOps: "aud": "499b84ac-1321-427f-aa17-267ca6975798" In

问题 ADAL.js and AAD v1 works to access Azure DevOps using delegated user_impersonation scope. I used the same AAD Application Id with delegated permissions to generate access tokens using MSAL.js. The tokens were created successfully, but the access token does not work to access Azure DevOps. The only meaningful difference in the decoded JWT token is that the "aud" claims are different. In ADAL/v1, the aud is the application id of Azure DevOps: "aud": "499b84ac-1321-427f-aa17-267ca6975798" In

问题 ADAL.js and AAD v1 works to access Azure DevOps using delegated user_impersonation scope. I used the same AAD Application Id with delegated permissions to generate access tokens using MSAL.js. The tokens were created successfully, but the access token does not work to access Azure DevOps. The only meaningful difference in the decoded JWT token is that the "aud" claims are different. In ADAL/v1, the aud is the application id of Azure DevOps: "aud": "499b84ac-1321-427f-aa17-267ca6975798" In

问题 ADAL.js and AAD v1 works to access Azure DevOps using delegated user_impersonation scope. I used the same AAD Application Id with delegated permissions to generate access tokens using MSAL.js. The tokens were created successfully, but the access token does not work to access Azure DevOps. The only meaningful difference in the decoded JWT token is that the "aud" claims are different. In ADAL/v1, the aud is the application id of Azure DevOps: "aud": "499b84ac-1321-427f-aa17-267ca6975798" In

来源： https://stackoverflow.com/questions/64510998/get-upn-and-email-address-from-msal-2-0-tokens

来源： https://stackoverflow.com/questions/64450218/why-http-401-when-calling-aspnet-core-api-secured-with-aad-our-webapp-web-api

来源： https://stackoverflow.com/questions/59790209/issuer-in-access-token-from-azure-active-directory-is-https-sts-windows-net-wh

来源： https://stackoverflow.com/questions/43332770/azure-active-directory-v2-0-daemons-and-server-side-apps-support

来源： https://stackoverflow.com/questions/49362631/msal-aadb2c90146-openid-profile-provided-in-request-specifies-more-than-on