msal

问题 I have an angular application hosted in Azure web app. I have selected azure active directory as the authentication provider and if the request is not authenticated then it should log in with the same. So, basically, if the user is already logged in with his/her Microsoft account then he/she does not need to log in again. As per now, I am using .auth/me to get all the user-related details such as givenName, email, etc. Now, I have a requirement to display the user's outlook profile picture.

问题 I'm developing an application in React, I'm using MSAL for the application login and once the user is authenticated I want to use the card component of a person but I can't make it work. I tell you what I have implemented in case I forgot some steps. I have added the following tag in the component itself: <mgt-msal-provider client-id={process.env.REACT_APP_MSALCLIENTID}></mgt-msal-provider> where that client I'm using on MSal to authenticate the user. I have also tried to define it in the

问题 I try to use the quickstart of sign-in with Microsoft but when I try to log an error appear: in my config file i have this parameters: and in the app config i have this paramter: i dont know what is happening :( Thanks for the help! :D 回答1: Your Redirect_Path should be same with azure portal Redirect URIs . Note: Protocol matters. AAD will treat http://localhost/logfinal/ and https://localhost/logfinal/ as different reply URLs. If you are still having an issue after following the steps above,

问题 I got error but all access in azure is ok. maybe my endpoint is wrong? Have you got any idea? Error APP_TEST needs permission to access resources in your organization that only an admin can grant. Please ask an admin to grant permission to this app before you can use it. I use this example TenanId = 11111111 ClientID = 22222222 export const msalConfig = { authority: 'https://login.microsoftonline.com/11111111', clientId: '22222222', redirectUri: document.getElementById('root').baseURI }; and

问题 I got error but all access in azure is ok. maybe my endpoint is wrong? Have you got any idea? Error APP_TEST needs permission to access resources in your organization that only an admin can grant. Please ask an admin to grant permission to this app before you can use it. I use this example TenanId = 11111111 ClientID = 22222222 export const msalConfig = { authority: 'https://login.microsoftonline.com/11111111', clientId: '22222222', redirectUri: document.getElementById('root').baseURI }; and

问题 I got error but all access in azure is ok. maybe my endpoint is wrong? Have you got any idea? Error APP_TEST needs permission to access resources in your organization that only an admin can grant. Please ask an admin to grant permission to this app before you can use it. I use this example TenanId = 11111111 ClientID = 22222222 export const msalConfig = { authority: 'https://login.microsoftonline.com/11111111', clientId: '22222222', redirectUri: document.getElementById('root').baseURI }; and

问题 So, I am trying to do see if I can support a scenario where a C# daemon app can access a custom Web API protected with MSAL.NET and OAuth2 scopes. As of now, I see no way of doing this. The versions of the libraries and toolsets are: .NET Core 2.2 Microsoft.Identity.Client 4.1.0 The client is var app = ConfidentialClientApplicationBuilder.Create("<app_id_of_my_web_api>") .WithClientSecret("<client_secret>") .WithAuthority("https://login.microsoftonline.com/<tenant_id_that_hosts_the_web_api>")

问题 In the Single Sign-On for Teams I have the call microsoftTeams.authentication.getAuthToken(authTokenRequest); working; that is, it successfully returns a token resolving to my Azure Active Directory (AAD) successfully. All good. Surprisingly easy. JWT returns with correct audience and scopes (as I have set in my tenant's AAD) However what I get back when I decode the JWT this seems to just be an Authentication Token, not an Access Token. Looking at the sample at Task Meow/teams.auth.service

问题 In the Single Sign-On for Teams I have the call microsoftTeams.authentication.getAuthToken(authTokenRequest); working; that is, it successfully returns a token resolving to my Azure Active Directory (AAD) successfully. All good. Surprisingly easy. JWT returns with correct audience and scopes (as I have set in my tenant's AAD) However what I get back when I decode the JWT this seems to just be an Authentication Token, not an Access Token. Looking at the sample at Task Meow/teams.auth.service

问题 I am using MSAL to acquire token from an auth app in Azure using integrated windows authentication. The code is: var tenant = $"https://login.microsoftonline.com/<myTenantId>"; var clientId = "<myClientId>"; var scopes = new string[] { "https://graph.microsoft.com/.default" }; var publicApplication = PublicClientApplicationBuilder.Create(clientId).WithAuthority(tenant).Build(); var token = await publicApplication.AcquireTokenByIntegratedWindowsAuth(scopes).ExecuteAsync(); This throws the