Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationQuestionQuestion
Previous
 
Next
New Post
11/9/2006 11:29 AM
 

Hi again,

 

Sorry for the duplicate post but after reading this thread after the othe recent one, this seems like a better venue perhaps. I am not a coder per se but can follow directions tollerably well and have a great vested interest in getting some of these VPN bugs worked out. I will gladly try to help test some of the solutions you folks are working on. Below is a copy of the issues I raised and my test observations.

Hal

 

I've been following this thread with great interest, looks like the AD module group could benefit from picking up a few free agents. Maybe free radicals... I don't know... anyhowww...good work all the same!

I have been trying to work out some bugs from my intranet install. I have 4.3.5 on a development instance of DNN on my webserver. I am having cookie/timeout  issues when connecting to my intranet via a Citrix/Net6 VPN connection. I have several test users in my AD which I have repeatedly auto registered and logged in from within my LAN so I know they are working.  (I then delete them to retest). I have applied the AD fixes of Stuart's/Mike's successfully. Here are the issues:

1. I'm working from a couple different remote clients, one across cable modem and one via DSL. In one case (DSL), I get an additional login prompt to the webserver even though I've listed it in my intranet zone. (I have tried adding this to my group policy as per Dan in another thread with mixed success; works better for internal connections than VPN)

2. When I've auto-logged in successfully as one user and then logged out to unauthenticated and then tried to log on as a different VPN user, but from the same remote machine, I either get authenticated as the first user of the auto register/login fails and I end up with the default unauthenticated page. I have manually deleted the cookie in question which seems to be geared to expire based on one of two cookie timeout settings in web.config ( 60 or 100000 minutes) but if I change those default values, it still creates cookie for 60 min. I've even deleted the first user account, logged on as someone else and it auto authenticates as the deleted account... repeatedly, even with cookie deletes in between. Is there another setting elsewhere? Is there a way to avoid deleting the cookie each time? The auto login seems to work fine within the WAN even for users from another domain with a trust relationship. Any suggestions about a. how to avoid the cookie, b how to get the authentication to happen reliably, after logging out as one person and logging back on the same machine as someone else?

I know you guys are focused elsewhere at the moment but any help would be appreciated. I may even be able to contract services for someone with some workable solutions.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationQuestionQuestion


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out