[
http://jira.nuxeo.org/browse/NXP-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67757#action_67757
]
Damien Metzler commented on NXP-4585:
-------------------------------------
The problem is not due to an invalid rpcToken map, but because of some weird
bugs using #rpctoken in url to pass the token.
Passing the token in the URL is better since the url is computed server side.
It seems to be a better choice (cf
http://issues.apache.org/jira/browse/SHINDIG-158)
> Set the map of auth thoken for each Gadget's IFrame
> ---------------------------------------------------
>
> Key: NXP-4585
> URL: http://jira.nuxeo.org/browse/NXP-4585
> Project: Nuxeo Enterprise Platform
> Issue Type: Improvement
> Reporter: Damien Metzler
> Priority: Major
>
> In the OpenSocial container, when the gadget wants to communicate with its
> parent (for instance to change the gadget height), it uses a rpc
> communication channel. This channel relies on auth token that are not well
> handled. It can result in a "invalid auth token" javascript error on some
> gadgets.
> This relies on the setAuthToken method of the Shindig RPC implementation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
