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 ForumsAuthenticationAuthenticationActive Directory Auth / semi-workingActive Directory Auth / semi-working
Previous
 
Next
New Post
7/13/2011 9:58 AM
 
Hi.  I'm having an issue with v5.0.3 (and also v5.0.2) of the AD auth module in DNN v5.6.2.  I can successfully login as an AD user.  But, depending on which AD user I login as, I very often get kicked out (redirected to login.aspx?returnpath=blah+blah)

I can make it happen pretty consistently.  After logging in, I click on a link to a custom page we have made.  It's basically an iframe, with a aspnet app inside it.  If I attempt to do anything on that page which involves a postback, I will get sent back to login.aspx?... and all page data is lost.  Also, if I just click the same link to get to this custom page, I will be redirected to login.aspx.  It does not happen for all AD accounts, only one that I've narrowed down so far.  The account is basically just a dupe of my own account (my account works, the dupe doesn't).  It also seems to happen for many of our custom pages, but also on standard DNN pages; but it is less consistently troublesome on std pages.  Btw, theres nothing about AD auth in these particular custom pages.

The strange thing about this is that we have 2 separate portals set up on the same box, with the same db backend.  They both have this same custom page link.  But it only happens on one of our portals, not the other one.  One portal never seems to have this issue; the other portal can't seem to get away from it.



I tried searching through the forums, and I may not be phrasing my searches well.  The closest issue I can find is from a few years back, and the resolution involved lowercase'ing both sides of a string comparison somewhere.  But, near as I can tell, that doesn't seem to be the problem here.  I even tried updating the users and aspnet_users tables to all lowercase, and making sure to login with a lowercase username, but that doesn't seem to help either.  can someone help me out here?
 
New Post
7/13/2011 3:49 PM
 
Is it possible that the user is spending all the time on the iframe application without clicking anywhere else on DNN, causing login to expire.

Ash Prasad
Director of Engineering
DNN Corp.
 
New Post
7/13/2011 4:42 PM
 
actually no.  its definitely not a timeout.  the issue can come up within 60 seconds.  when i test out this issue, i just click on a link.  wait for it to load.  click the same link, and bam, i'm logged out.
 
New Post
7/13/2011 5:48 PM
 
Does the iframe application uses Windows Authentication as well? I am wondering if AD authentication is colliding with that application. Do you experience log out if you log in as standard DNN user (and not AD, e.g. host).

Ash Prasad
Director of Engineering
DNN Corp.
 
New Post
10/29/2013 11:45 AM
 
Did you ever resolve this? I have a related issue. iframe in custom module breaks ad authentication and user is logged out.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationActive Directory Auth / semi-workingActive Directory Auth / semi-working


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