Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC
Open Closed

TokenProvider error after upgrading #2198


User avatar
0
terry bentley created

I just upgraded the Abp and ASPNet Zero to 1.2.0 after not upgrading for a few months. I think I made all the breaking change adjustments in the code and database but I must have missed something as I am getting the following error when I try to run it IUserTokenProviderAccessor should be instance of OwinUserTokenProviderAccessor!

App_Start\Startup.cs at the line app.RegisterDataProtectionProvider()

Any guidance as to where to look would be appreciated. Terry


3 Answer(s)
  • User Avatar
    0
    terry bentley created

    Sorry - I solve the problem. Never fails that I spend hours trying to resolve the issue myself and then as soon as I post I see the problem.

    In this case, I forgot to enter the [DependsOn( typeof(AbpZeroOwinModule),... in the WebModule class

    Still having an issue with the following entries in the Log file but will need to work through that (unless someone know the answer)

    WARN 2016-12-29 16:15:14,416 [25 ] ity.AntiForgery.AbpMvcAntiForgeryManager - The provided anti-forgery token was meant for a different claims-based user than the current user. WARN 2016-12-29 16:15:14,578 [25 ] rity.AntiForgery.AbpAntiForgeryApiFilter - Empty or invalid anti forgery header token. WARN 2016-12-29 16:15:14,748 [25 ] rity.AntiForgery.AbpAntiForgeryApiFilter - Requested URI: <a class="postlink" href="http://localhost:6234/api/services/app/session/GetCurrentLoginInformation">http://localhost:6234/api/services/app/ ... nformation</a>

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi,

    Do you use Internet Explorer for your tests ? Because there was a know bug for IE and we have fixed it here <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero/issues/395">https://github.com/aspnetzero/aspnet-zero/issues/395</a>.

    By the way, you can write all of your questions to premium forum section as well.

  • User Avatar
    0
    terry bentley created

    Hi - the problem was occurring with a basic login (not impersonation). It also happened on all browsers I tried.

    I found a few more differences in files between what I had and the new version of the Abp and was able to resolve the anti-forgery token error.

    Everything seems to now be working.

    Thanks... Terry