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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...07.03.04 All Request Redirect to Login07.03.04 All Request Redirect to Login
Previous
 
Next
New Post
2/4/2015 11:31 PM
 

I'm performing the upgrade from 07.00.02 to 07.03.04 in a development environment and post installation any attempts to load the home page on any portal results in a redirects to the login page.  These home pages are all configured to grant the 'All Users' role view access.

I've  altered many web.config settings regarding authentication to prevent the redirect from occurring but have had no success in stopping this behavior.  Has anyone else experienced this issue?

The IIS log show the initial GET request is to the default.aspx page and this is resulting in a 302 response from the server and an additional GET request to the login page, please see below:

2015-02-05 04:22:04 127.0.0.1 GET /default.aspx - 443 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.3;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/40.0.2214.94+Safari/537.36 - 302 0 0 6495

2015-02-05 04:22:04 127.0.0.1 GET /Default.aspx TabId=672&ctl=Login&returnurl=%2fdefault.aspx 443 - 127.0.0.1 Mozilla/5.0+(Windows+NT+6.3;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/40.0.2214.94+Safari/537.36 - 200 0 0 439


 

 
New Post
2/5/2015 6:54 AM
 
the 302 is a simple response.redirect which occurs because DNN thinks the user has no permissions on the page -without the ability to view the page it's hard to say what it might be e.g. a deny view permission or something else

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
2/6/2015 12:08 AM
 

Thanks Cathal but I've reviewed the page permissions and they're are correct for the landing pages.  This issue is also present in sites that have basically been configured as public sites so all the modules allow anonymous access.

My portals have been dramatically customised (the dbo.Version table contains 90 records back to version 1.3.1 in 2006) and there may be a module (something like the search module) programmatically removed from the page that’s now included again because I've not merged the customisation back in post upgrade.  Given I spotted the issue fairly early in the development of my upgrade procedure I'm holding back on merging any customisation until the portals are stable.

There doesn’t appear to be any noise about other developers experiencing this behaviour with this version (historically there have been but they’re generally configuration issue) so I must be looking at something resulting from a customisation.

 
New Post
2/10/2015 10:54 PM
 
Here's the solution and an explanation of the root cause of the issue.

There appears to be a change in the DNN framework between versions 07.00.02 and 07.04.00 where the RoleName from dbo.vw_TabPermissions is being used instead of the RoleId in the same view. This is being returned by the dbo.GetTabPermissionsByPortal stored procedure. In 07.00.02 I've not had any issues but after the upgrade given there's some legacy data in the dbo.Roles table for RoleId -1 that was created at a time when the -1, -2 and -3 system roles did no appear to exist. The in my system was a non-system roles created for some custom functionality hence the RoleName was not 'All Users'.

Updating the RoleName field to 'All Users' corrects the issue and looking at old backups when the system was at version 05.06.03 there were no records in my database for RoleIds -1, -2 and -3. Historically the Roles appear to have been hard-coded in most places like they still are now in dbo.vw_TabPermissions at version 07.04.00.

So, the root cause was bad data identified with the SQL Profiler after a lot of debugging .Net code where the problem didn't exist.

 
New Post
2/11/2015 4:27 AM
 
I added virtual roles -1, -2 and -3 for All Users, Superusers and unauthenticated users in DNN 7.1 into the database, but they are filtered by all view / procedures not to be returned to the DNN API (which re-adds them internally). The role codes had been used in permissions tables before, this was just to be able to enforce refential integrity. None of the API should rely on any role Name, if you experience this, please log at Support.dnnsoftware.com, thank you.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...07.03.04 All Request Redirect to Login07.03.04 All Request Redirect to Login


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