adal

I am trying to write an WPF client which uses ADAL to authenticate against ADFS on a Windows Server 2012 R2. I have successfully implemented this using "Forms Authentication" where the user is prompted for the domain username and password. However, I want to take advantage of SSO and use the currently logged on domain user to authenticate against the ADFS. Unfortunately, I'm only getting an error message saying: This method overload is not supported by '< ADFS servername>' I have done a lot of searching, but find some of the information contradictive: This SO post about a Windows Store App

I have an API app that has been working fine with a Gateway Host and now that the gateway host is being deprecated I'm trying to follow the Migration Guide . I've redeployed my service using the 2.8.1 SDK and can log into the service with a browser using AAD or a Microsoft account and use Swagger to test the service. However, I'm trying to get a client to access the service using a ClientId and Secret. The code is able to get the access token from AAD but I always get a 401 error whenever I try to access one of the service resources. When I debug the service I see the following in the log:

I am trying to handle authentication for my app which uses Microsoft Graph. What is the difference between these two libraries? Active Directory Authentication Library for JavaScript (ADAL.js) Microsoft Authentication Library for JavaScript (MSAL.js) Is ADAL.js just an Angular 1 library of MSAL.js? MSAL.js works with the AzureAD V2 endpoint, whereas ADAL.js works with the AzureAD V1 endpoint. The V1 endpoint supports work accounts, but not personal accounts. The V2.0 endpoint is the unification of Microsoft personal accounts and work accounts into a single authentication system. Finally, with

Why won't my Azure AD application allow an oauth client_credentials grant? I want to use the Azure Graph API, but first I need an oauth token. To get the token, I am trying to use Microsoft.IdentityModel.Clients.ActiveDirectory aka ADAL version 1.0.3 (from NuGet). I'm using the overload of AuthenticationContext.AcquireToken that takes a ClientCredential object. (I can't use the overload that prompts the user to login because I'm writing a service, not an app.) I configured my Azure AD web application as described in various tutorials/samples (e.g. ADAL - Server to Server Authentication ). My

I'm trying to authenticate my SPA (angular.js and adal.js (similar to the https://github.com/Azure-Samples/active-directory-angularjs-singlepageapp-dotnet-webapi example) My AD is a azure b2c preview tenant. I can successfully log in to my webapi from my Website, but not from the JS SPA via angular. My Setup: Webapi and Website share the same clientid (does only seem to work this way) The SPA has its own clientid, because otherwise i get "api version not supported" errors when trying to log in. I have enabled oauth2AllowImplicitFlow for all applications, granted application permissions from

How can you configure ADAL JS to use an on-premise Active Directory (Windows Server 2012 R2, ADFS)? The announcement post ( http://www.cloudidentity.com/blog/2014/10/28/adal-javascript-and-angularjs-deep-dive/ ) and samples on GitHub ( https://github.com/AzureADSamples ) do not specifically address this. Or is that not a supported scenario? this is currently not supported. ADFS does not support the oauth2 implicit grant, which is at the heart of the scenario With ADFS 4.0 and Windows Server 2016 this is now possible, you can use adal.js as is for authentication of users on on-premise ADFS 来源：

In ADAL.Net 3.x UserPasswordCredential is introduced on top of UserCredential from 2.x. But the same UserPasswordCredential is not exposed in the .Net Core under the same nuget package? UserCredential class has only one property UserName namespace Microsoft.IdentityModel.Clients.ActiveDirectory { // // Summary: // Credential used for integrated authentication on domain-joined machines. public class UserCredential { // // Summary: // Constructor to create user credential. Using this constructor would imply integrated // authentication with logged in user and it can only be used in domain joined

We have front end developed in AngularJS and backend APIs in NodeJs. We are using Azure AD for authentication. Frontend Angular is using adal-angular javascript library for azure authentication. So when user comes to web site, he gets redirected to https://login.microsoftonline.com and upon successful authentication he gets redirected back to our web site. So far so good. I have to protect backend api’s using passport-azure-ad library. Only the frontend is calling these APIs. There are two strategies available using this library 1> OAuth2Bearer strategy 2> OIDCStrategy for Open ID Connect I