Hello there,
I'm sorry for this old question and also for not knowing how to categorize it in terms of Forum.

When I click on the hyperlinks in htmlDataGrid, the links work fine in the same tab but when I try to open them in a new tab they some how loose the authentication and are redirected to the login page.
I'm sure I'm missing something but before I spend too much time on diving into the old codes, I would like to know if anyone has any hint or tips on this.

Thank you so much in advance,
Kathy

You shouldn't be losing auth on a new tab in the same browser - assuming the following:

• You're staying on exactly the same Web site
• Same exact domain (ie. mysite.com and www.mysite.com are different even if same site)
• Same http:// or https://
• You're not opening a Private tab

+++ Rick ---

Thank you so much Rick.
I'm in the same website and it's the same link, it's just clicking on the links and launching the corresponding page in the same tab vs. right-clicking on it and choosing the "Open link in new tab", even copy-pasting the link address doesn't work so I think it could be my mistake somewhere in the customizations, etc.
I'll go through the codes to see if I can find the reason.
Thanks again for the helpful tips.
Kathy

Check for the Cookie in the request data coming in. If the cookie is not there, then the auth is not going to work. If you lose the cookie in the transition from tab to tab, but it works if you navigate inside the same window there might be something else happening that's killing the cookie (ie. some browser plug-in or Anti-Virus) that explicitly prohibits that behavior.

You can use the Request Viewer in the Web Connection server after you check full request logging, or use the Browser Developer tools and the network tab with the Preserve Log checkbox on. Then look at the Doc page and the Request Headers -> Cookie. You'll want to make sure that that cookie you see stays the same and doesn't change or disappear.

+++ Rick ---

Thank you for the detailed instruction for debugging this Rick.
And yes, it looks like the cookie gets lost, and actually launching a new tab, enforces and redirects the page to logout! I also did some tests on different browsers and different computers but the issue is still there, so I think it might be the confirmation for there should be a breakage in the code.
Thank you again.
Kathy

LOL - yeah if you log out that would account for it 😄

Web Connection's auth will detect if there's no login or an invalid login, and then jump to the login form (and also kill the cookie). But that would first have to detect a bad cookie that can't be matched. If you follow the flow you should be able to detect where exactly you are losing the cookie - is it on the very first request that hits the new tab, or is it after when the redirect and logout occurs. If there's a cookie to start on the new tab, see if you can debug that request and see why the cookie is not validating against what you have in the db by stepping through the Web Connection authentication code.

+++ Rick ---