Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
I am trying to set up an impersonation feature on our site that allows the admin to revert when they are done. The impersonation part works fine, but reverting is a problem. When I try to revert, it fails because the admin is "already logged in." I don't want to log the admin out until I know that that they can successfully impersonate. As far as I can tell, this can only be determined when AuthenticateUser is called. If successful, at that point we are using the impersonated user's account. If the impersonated user is not an admin, I have not been able to find a way to log out the impersonating admin's account and let them reauthenticate.
Does anyone have an idea how to get around this?
I could create another admin account, but that carries its own set of issues
Hi Brian. Not sure if it will helps for you, but you can try to enable self-logout "Automatically logout backend users from other HTTP clients on login"