I'm getting an error when using the impersonate login feature from the host to a tenant.
When I log in to the host environment, login to a tenant through the impersonation function, I recieve the following error:
System.Exception: Current tenant is different than given tenant. AbpSession.TenantId: , given tenantId: 37 at Robin.Authorization.Impersonation.ImpersonationManager.CheckCurrentTenant(Nullable
1 tenantId)
at Robin.Authorization.Impersonation.ImpersonationManager.d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Robin.Web.Controllers.AccountController.d__51.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Abp.Threading.InternalAsyncHelper.d__51.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at lambda_method(Closure , Object ) at Microsoft.Extensions.Internal.ObjectMethodExecutorAwaitable.Awaiter.GetResult() at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.TaskOfActionResultExecutor.<Execute>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeActionMethodAsync>d__12.MoveNext() --- End of stack trace from previous
<br> This problem only occurs on macOS devices with the Safari browser. Anyone got a clue why this is happening, and how we may fix this?
Version: Asp.Net Core MVC version v5.2.0 but we updated all the packages to the latest version a few weeks ago.
Device: Macbook Pro macOS High Sierra. Safari version 12.0
Thanks!!
2 Answer(s)
-
0
May be a problem with browser cookies, You can try the chrome browser under macos.
-
0
Actually fixed it. The application URL changed in IIS, so what happened was that on impersonated login the url went from http://a.blabla to http://b.blabla. Which works on most browsers but not on Safari.