|
Home > Archive > Microsoft Content Management Server > August 2004 > Authentication Token Failure Stack Trace
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Authentication Token Failure Stack Trace
|
|
| Chris Surguine 2004-08-17, 5:50 pm |
| Hi,
I am trying to find out where in my templates / channel
rendering scripts I am referencing
CmsHttpContext.Current, which evidently is triggering an
unhandled exception: Login failed due to invalid or
expired authentication token. I have placed try/catch
blocks around the onInit and PageLoad events for every
class related to the MCMS login page, but the error still
continues. I am using Forms-based authentication instead
of Windows-based - could this be part of the problem?
Here is the stack trace:
-----------------------------------------------------
Logon failed due to invalid or expired authentication
token.
Description: An unhandled exception occurred during the
execution of the current web request. Please review the
stack trace for more information about the error and
where it originated in the code.
Exception Details:
System.Runtime.InteropServices.COMException: Logon failed
due to invalid or expired authentication token.
Source Error:
An unhandled exception was generated during the execution
of the current web request. Information regarding the
origin and location of the exception can be identified
using the exception stack trace below.
Stack Trace:
[COMException (0x80041bf0): Logon failed due to invalid
or expired authentication token.]
Microsoft.ContentManagement.Interop.Publishing.CmsHttpCont
extClass.Initialize(String currentUrl, String
httpHostName, Int32 serverPort, Boolean isSecureServer,
Int32 iisInstanceId, String remoteMachineAddress, String
authenticationType, String authenticationToken, Int32
windowsUserHandle, String ClientAccountName) +0
Microsoft.ContentManagement.Publishing.CmsHttpContext.init
ialize(IntPtr windowsToken, String cmsAuthToken, String
clientUserName, String clientAccountType) +297
Microsoft.ContentManagement.Publishing.CmsHttpContext.getC
msHttpContextFromIdentity(HttpContext httpContext)
+1088
Microsoft.ContentManagement.Publishing.CmsHttpContext.get_
Current() +57 [CmsAccessDeniedException: The CMS
authentication token is invalid or expired. If you are
seeing this exception when a CMS template is executing,
it means that you have removed the CmsAuthorizationModule
from the <httpModules>...</httpModules> section of your
web.config. You can only remove this module if: 1. All
requests for every CMS template in the web application
will only be accessed by anonymous users 2. Guest access
is enabled in CMS (via the SCA) 3. The CMS guest user has
access to all postings based on templates in the web
application If any of these requirements are not met,
you MUST register the CmsAuthorizationModule in your
web.config.]
Microsoft.ContentManagement.Publishing.CmsHttpContext.get_
Current() +251
Microsoft.ContentManagement.WebControls.WebAuthorContext.E
valuateMode() +7
Microsoft.ContentManagement.WebControls.ConsoleControls.Pr
oductionManagerAction.OnInit(EventArgs e) +25
System.Web.UI.Control.InitRecursive(Control
namingContainer) +240
System.Web.UI.Control.InitRecursive(Control
namingContainer) +178
System.Web.UI.Control.InitRecursive(Control
namingContainer) +178
System.Web.UI.Control.InitRecursive(Control
namingContainer) +178
System.Web.UI.Control.InitRecursive(Control
namingContainer) +178
System.Web.UI.Control.InitRecursive(Control
namingContainer) +178
System.Web.UI.Control.InitRecursive(Control
namingContainer) +178
System.Web.UI.Page.ProcessRequestMain() +174
Version Information: Microsoft .NET Framework
Version:1.1.4322.573; ASP.NET Version:1.1.4322.573
-------------------------------------------------------
Any help you can offer would be great!
Regards,
Chris
| |
| Stefan [MSFT] 2004-08-17, 5:50 pm |
| Hi Chris,
please check this article:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#53EB2F9B-E87E-442C-8D69-B2B0B783EBB8
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
MCMS FAQ:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...t+S
erver
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------
"Chris Surguine" <csurguine@nospam--dunnsolutions.com> wrote in message
news:7d0501c4846c$531f4870$a601280a@phx.gbl...
> Hi,
>
> I am trying to find out where in my templates / channel
> rendering scripts I am referencing
> CmsHttpContext.Current, which evidently is triggering an
> unhandled exception: Login failed due to invalid or
> expired authentication token. I have placed try/catch
> blocks around the onInit and PageLoad events for every
> class related to the MCMS login page, but the error still
> continues. I am using Forms-based authentication instead
> of Windows-based - could this be part of the problem?
> Here is the stack trace:
>
> -----------------------------------------------------
>
> Logon failed due to invalid or expired authentication
> token.
> Description: An unhandled exception occurred during the
> execution of the current web request. Please review the
> stack trace for more information about the error and
> where it originated in the code.
>
> Exception Details:
> System.Runtime.InteropServices.COMException: Logon failed
> due to invalid or expired authentication token.
>
> Source Error:
>
> An unhandled exception was generated during the execution
> of the current web request. Information regarding the
> origin and location of the exception can be identified
> using the exception stack trace below.
>
> Stack Trace:
>
> [COMException (0x80041bf0): Logon failed due to invalid
> or expired authentication token.]
> Microsoft.ContentManagement.Interop.Publishing.CmsHttpCont
> extClass.Initialize(String currentUrl, String
> httpHostName, Int32 serverPort, Boolean isSecureServer,
> Int32 iisInstanceId, String remoteMachineAddress, String
> authenticationType, String authenticationToken, Int32
> windowsUserHandle, String ClientAccountName) +0
> Microsoft.ContentManagement.Publishing.CmsHttpContext.init
> ialize(IntPtr windowsToken, String cmsAuthToken, String
> clientUserName, String clientAccountType) +297
> Microsoft.ContentManagement.Publishing.CmsHttpContext.getC
> msHttpContextFromIdentity(HttpContext httpContext)
> +1088
> Microsoft.ContentManagement.Publishing.CmsHttpContext.get_
> Current() +57 [CmsAccessDeniedException: The CMS
> authentication token is invalid or expired. If you are
> seeing this exception when a CMS template is executing,
> it means that you have removed the CmsAuthorizationModule
> from the <httpModules>...</httpModules> section of your
> web.config. You can only remove this module if: 1. All
> requests for every CMS template in the web application
> will only be accessed by anonymous users 2. Guest access
> is enabled in CMS (via the SCA) 3. The CMS guest user has
> access to all postings based on templates in the web
> application If any of these requirements are not met,
> you MUST register the CmsAuthorizationModule in your
> web.config.]
> Microsoft.ContentManagement.Publishing.CmsHttpContext.get_
> Current() +251
> Microsoft.ContentManagement.WebControls.WebAuthorContext.E
> valuateMode() +7
> Microsoft.ContentManagement.WebControls.ConsoleControls.Pr
> oductionManagerAction.OnInit(EventArgs e) +25
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +240
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +178
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +178
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +178
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +178
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +178
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +178
> System.Web.UI.Page.ProcessRequestMain() +174
>
> Version Information: Microsoft .NET Framework
> Version:1.1.4322.573; ASP.NET Version:1.1.4322.573
>
> -------------------------------------------------------
>
> Any help you can offer would be great!
>
> Regards,
>
> Chris
>
| |
| Glen Wells 2004-08-18, 7:51 am |
| Do you reference CmsHttpContext.Current in the page defined as your logon
page in web.config?
<authentication mode="Forms">
<forms loginUrl="/myapp/logonpage.aspx" />
</authentication>
--
Glen Wells
www.cubik.co.uk
"Chris Surguine" <csurguine@nospam--dunnsolutions.com> wrote in message
news:7d0501c4846c$531f4870$a601280a@phx.gbl...
> Hi,
>
> I am trying to find out where in my templates / channel
> rendering scripts I am referencing
> CmsHttpContext.Current, which evidently is triggering an
> unhandled exception: Login failed due to invalid or
> expired authentication token. I have placed try/catch
> blocks around the onInit and PageLoad events for every
> class related to the MCMS login page, but the error still
> continues. I am using Forms-based authentication instead
> of Windows-based - could this be part of the problem?
> Here is the stack trace:
>
> -----------------------------------------------------
>
> Logon failed due to invalid or expired authentication
> token.
> Description: An unhandled exception occurred during the
> execution of the current web request. Please review the
> stack trace for more information about the error and
> where it originated in the code.
>
> Exception Details:
> System.Runtime.InteropServices.COMException: Logon failed
> due to invalid or expired authentication token.
>
> Source Error:
>
> An unhandled exception was generated during the execution
> of the current web request. Information regarding the
> origin and location of the exception can be identified
> using the exception stack trace below.
>
> Stack Trace:
>
> [COMException (0x80041bf0): Logon failed due to invalid
> or expired authentication token.]
> Microsoft.ContentManagement.Interop.Publishing.CmsHttpCont
> extClass.Initialize(String currentUrl, String
> httpHostName, Int32 serverPort, Boolean isSecureServer,
> Int32 iisInstanceId, String remoteMachineAddress, String
> authenticationType, String authenticationToken, Int32
> windowsUserHandle, String ClientAccountName) +0
> Microsoft.ContentManagement.Publishing.CmsHttpContext.init
> ialize(IntPtr windowsToken, String cmsAuthToken, String
> clientUserName, String clientAccountType) +297
> Microsoft.ContentManagement.Publishing.CmsHttpContext.getC
> msHttpContextFromIdentity(HttpContext httpContext)
> +1088
> Microsoft.ContentManagement.Publishing.CmsHttpContext.get_
> Current() +57 [CmsAccessDeniedException: The CMS
> authentication token is invalid or expired. If you are
> seeing this exception when a CMS template is executing,
> it means that you have removed the CmsAuthorizationModule
> from the <httpModules>...</httpModules> section of your
> web.config. You can only remove this module if: 1. All
> requests for every CMS template in the web application
> will only be accessed by anonymous users 2. Guest access
> is enabled in CMS (via the SCA) 3. The CMS guest user has
> access to all postings based on templates in the web
> application If any of these requirements are not met,
> you MUST register the CmsAuthorizationModule in your
> web.config.]
> Microsoft.ContentManagement.Publishing.CmsHttpContext.get_
> Current() +251
> Microsoft.ContentManagement.WebControls.WebAuthorContext.E
> valuateMode() +7
> Microsoft.ContentManagement.WebControls.ConsoleControls.Pr
> oductionManagerAction.OnInit(EventArgs e) +25
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +240
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +178
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +178
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +178
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +178
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +178
> System.Web.UI.Control.InitRecursive(Control
> namingContainer) +178
> System.Web.UI.Page.ProcessRequestMain() +174
>
> Version Information: Microsoft .NET Framework
> Version:1.1.4322.573; ASP.NET Version:1.1.4322.573
>
> -------------------------------------------------------
>
> Any help you can offer would be great!
>
> Regards,
>
> Chris
>
|
|
|
|
|