Geek Answers Handbook

How to disable work in DNN 5.x?

We see a problem when a session does not terminate in DNN. I'm not sure if this was a 4.5.x problem, as we updated some time ago to 5.x and may have referenced the old control.

The login / logout element that we refer to in our module is DotNetNuke.UI.Skins.Controls.Login, located along the DNN_Web_Root / admin / Skins / login.ascx path

It looks like it redirects to logoff.aspx, which then goes through the LogoffHttpHandler, which then goes somewhere to complete the logout process, however I cannot find where this process should see if Session.Abandon is called.

Can anyone answer the following:

  • Is there a problem with DNN where SessionAbandon is not called when logging out?
  • What is the process that actually processes the LogOff process?
+5
source share
3 answers

The output is usually processed using Desktopmodules \ Admin \ Authentication \ Logoff.ascx. The main action is to clear the authentication cookie, as well as some cookies and some user cached data.

DotNetNuke NEVER uses a session for anything and does not clear the session during logout.

+2
source

Dan Row seems to be lucky with the following code:

Response.Redirect(Globals.NavigateURL(TTSRoutines.giPunchinPage, "Logoff"), True)

Link

0
source

, , , - , - , , -, , - 20 ?

If you must use a session, one workflow is just to check

System.Web.HttpContext.Current.User.Identity.IsAuthenticated

anywhere, you are disturbed by an unclaimed user using the previously registered user session variables.

Talking about calling Session.Abandon () in the logout section, as @ScottS suggests, might be the easiest way, although this option might not be available in a hosted environment.

0
source

More articles:


All Articles