Skip to main content
Participant
September 25, 2012
Question

HTML5 widget trigger OpenAjax Invalid auth token. error

  • September 25, 2012
  • 1 reply
  • 1739 views

Hi,

I've been trying to build an html5 captivate widget following this documentation: http://help.adobe.com/en_US/captivate/cp/using/WSc1b83f70210cd101-39b1e31d11d86d8de77-8000.html#WS16484b78be4e1542-af1917b1379c6df159-7fff

I need help to figure out why I get this exception when I trigger an unload of my slide containing the widget.

  1. Invalid auth token. WLlSDh vs -fvXnT OpenAjaxManagedHub-all.js:1510
    1. OpenAjax.gadgets.log.logAtLevelOpenAjaxManagedHub-all.js:1510
    2. OpenAjax.gadgets.errorOpenAjaxManagedHub-all.js:1495
    3. _1f8OpenAjaxManagedHub-all.js:2107
    4. receiveSameDomainOpenAjaxManagedHub-all.js:2405

I've looked at http://www.openajax.org/whitepapers/Ajax%20and%20Mashup%20Security.php but this does not help me so far.

I'm running my test from my localhost. I don't understand where that OpenAjax code get triggered in the first place (since its a setTimeout that trigger the whole thing I can't see who even invoke it from the stack trace).

The other parts of the widget are working fine.

EDITED:

cp.Widget.prototype.doOpenAjaxLoading is the method that trigger the issue (CPWidgetManager.js) I get the onSecurityAlert but the exception remained unclear.

@1348586975737 widget doOpenAjaxLoading cliId = 4154 CPLibrary.js:122

  1. Invalid auth token. dOnTWr vs wYs2mT OpenAjaxManagedHub-all.js:1510

@1348586975760 onSecurityAlert: s=4154 a=OpenAjax.hub.SecurityAlert.ForgedMsg CPLibrary.js:122

@1348586975837 widget doOpenAjaxLoading _loaded 

In order -> I get cp.Widget.prototype.reset that invoke this.widget.onUnLoad();  and then OpenAjax.hub.IframeContainer trigger a security alert...

This topic has been closed for replies.

1 reply

Legend
September 25, 2012

The Adobe Documentation on widget building leaves a lot to be desired.  I would suggest at looking at the Stock Captivate Interactions that also publish to HTML5 and see how they've structured their JS and XML docs inside the WDGT file.  Seeing an example goes a long way.

Jim Leichliter

GMalartreAuthor
Participant
September 26, 2012

I already derived from A3C.wdgt found in the widget gallery bundled with Captivate. The problem does not seem to come from my widget itself but the way they implemented OpenAjax interoperability. I did not find any other wdgt file that publish to html5 in the gallery.

Often I can refresh my slide 3-4 times and the error never appear but if I play just enough with the refresh button the error get thrown.

Legend
September 26, 2012

The stock interactions in Cp 6 are actually widgets that do publish to HTML5.  Take a look at those.