adal

We are developing a multi-tenant web application. Our tenants will be using Windows Azure Active Directory for authentication. We are using OWIN OpenIdConnect middleware to authenticate users. The response we receive after authentication process has id_token and authorization code. We also want to get the refresh token so that we can acquire new tokens once the id_token expires. Therefore in AuthorizationCodeReceived handler we use AcquireTokenByAuthorizationCode method in ADAL library to acquire the refresh token. The response contains id_token, access_token and refresh_token. We then

I'm currently trying to hook in the Azure Directory Authentication Library (ADAL.JS) into UI-Router. I've got it wired in, and it redirects correctly, but it always chucks a 404 before the redirect. The redirect works, and then gets sent back to my application, which is showing the 404. I've modified the state like so: { state: 'admin', config: { url: '/admin', templateUrl: 'app/admin/admin.html', controller: 'AdminController', controllerAs: 'vm', title: 'Admin', settings: { nav: 2, content: '<i class="fa fa-lock"></i> Admin' }, requireADLogin: true } I've got it working with the normal

First of all, I'm not sure if this is important, but for the reasons mentioned by @ Simon Mourier in him answer , I'm using the EXPERIMENTAL build of ADAL, this one . In the code below, I would like to retrieve an AuthenticationResult synchronouslly, so, I will wait for completition of the authentication by AcquireTokenAsync method in a synchronous manner. This is because a boolean flag should be set after the authorization is done ( isAuthorized = true ), but tgis need to happen in a synchronous way, because if not, then I can call other methods of the class that will throw a null reference

I am using iOS ADAL library version 2.2.6 and receiving refresh token upon successful login. Now I want to make a silent call by using this refresh token. I tried with following method but it fails to return the access token. ADAuthenticationContext *authContext; [authContext acquireTokenSilentWithResource:resourceId clientId:clientId redirectUri:redirectUri userId:strUserID //loggedIn userID completionBlock:^(ADAuthenticationResult *result){ // It alway throws an error //Please call the non-silent acquireTokenWithResource methods. if(result.error){ ADAuthenticationError *error = nil;

I am using ADALiOS into my app for authentication. When user signIn into the app I am getting following error: "The argument 'cacheItem.scopes' is invalid. Value:(null)." and "The user credentials are need to obtain access token. Please call the non-silent acquireTokenWithResource methods" Any help would be appreciated. Thanks This might happen if keychain sharing is disabled. One of the probable solution is: Solution: Step 1: Xcode > Target > Capabilities > Keychain Sharing -> Switch to ON Step 2: add com.microsoft.adalcache into Keychain Group. Hope this helps. There is a pattern for dealing

We are using Azure AD to authenticate and get the refreshed access token every 30 mins. We invoke below method which acquires security token and add it to request header. var userObjectId = ClaimsPrincipal.Current.FindFirst("http://schemas.microsoft.com/identity/claims/objectidentifier").Value; var authContext = new AuthenticationContext(Authority, new NaiveSessionCache(userObjectId)); var credential = new ClientCredential(ConfigurationManager.AppSettings["ida:ClientId"], ConfigurationManager.AppSettings["ida:ClientSecret"]); try { var authenticationResult = authContext.AcquireTokenSilent

The Goal Access an on-premise SharePoint data with REST requests from a mobile application based on Apache Cordova using OAuth. What I have tried so far 1. Azure Mobile Services / Hybrid Connection / AAD / ADAL Similar to the blog post Access SharePoint on behalf of the user , but with an on-premise server instead of O365: Client side log-in using ADAL for Apache Cordova . Mobile Service that is connected to the on-premise server through hybrid connections. Using ADAL.net to acquire a token for the SharePoint server using the token obtained in step 1. This works fine except step three, since