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

Internal server error (500) on Impersonate Token on isolated azure environment (Token expired) #11382


User avatar
0
omkarchoudhari created

Hi

we have deployed our Prod in premium p2 v2 earlier (which is shared along with our UAT environment) and now we decided to move our same code to isolated Azure environment but this impersonate API is (this._accountService.impersonate) failing giving token expired error but after 1-2 Page refresh same token starts working. we did not faced this issue earlier on our previous environment we have tried to extend token time to 10 min but still failing initially on every login. let us know if any solution available.


6 Answer(s)
  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @omkarchoudhari

    Are you using memory cache or redis for your app ?

  • User Avatar
    0
    omkarchoudhari created

    Hi

    we are using Memory Cache provided by framework

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi,

    Is your app running as 1 instance or multiple instances ? If it is multiple instances, you need to use Redis instead of Memory cache.

    Thanks,

  • User Avatar
    0
    omkarchoudhari created

    Thank you.... it worked after using redis

  • User Avatar
    0
    omkarchoudhari created

    Hi we are having with signalR on the multi-instance production environment from error it seems like it get connected some times. but we not able to find exact issue and how to resolve this

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi,

    You need to follow https://docs.aspnetzero.com/en/aspnet-core-mvc/latest/Clustered-Environment#scaling-signalr and scale your SignalR using Redis.