AcquireTokenSilent

[azuread]

AcquireTokenSilent

[vibronet]

The feature is definitely implemented. Are you executing the example code precisely as is, or did you modify anything in it? Typical issues with AcquireTokenSilent in web scenarios are:

• The cache is empty. AcquireTokenSilent works by returning cached tokens or using refresh tokens from the cache. In the OpenId Connect samples, the application first acquires access and refresh tokens at sign in time and places them in a cache instance. If something happens to the cache between that time and the time in which you call AcquireTokenSilent, or if you fail to initialize AuthenticationContext with the exact same cache instance, the request will fail.
• The cache contains more than one token matching the parameters, for example for 2 different users. In that case ADAL needs more info (like the ID of the user you want ta token for) to disambiguate the request
• You are requesting a token from a new AAD tenant. Refresh tokens in the cache will work for requesting new tokens only from the same tenant they were originally issued from
  You can verify in which situation you are by inspecting the content of the cache before making your AcquireTokenSilent call, simply call myAuthContext.TokenCache.ReadItems and examine the results in the debugger.
  HTH

[rlongodev]

Hi Vittorio, thanks a lot for the quick response. You are right, I think I misunderstood the samples and my scenario its a little bit different. Thing is I didn't get a token before a call to AcquireTokenSilent.

Regards,
Rodrigo

[kpanwar]

If you use the latest 2.24 then you will get an inner exception that will tell you why acquire token silent failed. Can you check and share the details.