Developer forum

Forum » CMS - Standard features » Impersonation and pool recycle

Impersonation and pool recycle

António Ramos
Reply

Hi guys,

With a user X when we are impersonating a user Y and the pool recycles, the user X remains logged but lost the impersonation from user Y.
There is any way to workaround this? Perhaps store the impersonate session in cookie?

Best regards,

António Ramos


Replies

 
Jonas Krarup Dam
Reply
This post has been marked as an answer

Hey António.

I'd consider this a bug.

You should probably be able to do some javascript that keeps the impersonation alive, but I haven't tried it.

I'll create a bug in our system, and get it fixed.

Regards, Jonas

Votes for this answer: 1
 
António Ramos
Reply

Hi Jonas,

Thanks for your help! Have a nice day.

Best regards,

António Ramos

 
António Ramos
Reply

Hi Jonas,

Do you have any estimate in which version and date it will be released the bug fix?

Thanks,

BR António Ramos

 
Jonas Krarup Dam
Reply

Hi,

I have marked it for 8.8.1.x, so it should be in an upcomming hotfix on that version.

I do not have an estimate for when this hotfix will be out, as most of the office is on summer vacation. I would expect within 2-4 weeks, but I cannot promise anything right now.

Regards, Jonas

 
António Ramos
Reply

Hi Jonas,

I'm afraid that 2-4 weeks is too much for our client. You suggest the javascript as workaround. Can you give some guidelines (which field/cookie that needs stored) to solve this issue?

Thanks,

Best regards,

António Ramos

 
Jonas Krarup Dam
Reply

Hi Antonio.

Well, if it where me, I'd add some javascript code to the "Start impersonation" and "End impersonation" templates, that saves impersonation information in a cookie.

Then I'd add some javascript code to the main template that checks if an impersonation session is currently active in dynamicweb (Via the tags about primary and secondary user ids), and if not, check if a cookie exists to indicate an impersonation session should be active. In that case, I would do a reload, re-initializing the impersonation session, the same way it is currently done in the "start impersonation" template.

I would basically look at the global tags : Global:Extranet.UserID and  Global:Extranet.SecondaryUser.UserID All the time, to check if they have the expected values, and to activate impersonation if they don't

Hope this helps :-)

Regards, Jonas

 

You must be logged in to post in the forum