Hey everybody,

I've been googling and searching around forever for an answer to this and I think I've narrowed down the issue.

I have a main DNN Portal (let's call it Site1) and a Child portal of Site1 (let's call it Site1/child).

In Site1, there's a custom module that I've coded with a button. When that button is clicked, in the code behind, we essentially have:

Response.Write(<javascript..> window.parent.open(Site1/child?withsomeparams)</javascript.)

When the button is clicked, Site1/child opens fine and works fine. When I return to the Site1 window however, the Authentication Cookie is gone.

I've read that this is due to the fact that the Membership Module causes a clearing of the Authentication Cookie when there's a redirect to another portal. This is consistent because when I log in as host - I DON'T get this issue.

Furthermore, I only get this issue when my SITE is being hosted on SSL. On non-SSL, there's is no problem.

So basically, I'm pretty sure this is an Authentication Cookie issue - and it being cleared when there's a redirect. I'm on version 04.03.05 (and it might be a little hard for me to upgrade).

Is there an easy workaround. I heard something about passing the PortalId and ModuleID. If so, how would I do that?  - through params? if so what are the param names etc.? Again, keeping in mind that I'm using Response.Write("<script...javascript>window.parent.open(url)</script>") in the code-behind (the url is dynamically generated that's why it's being done in the code behind.

Any help would be greatly appreciated. Thanks.