[
https://jira.nuxeo.com/browse/NXP-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=88057#action_88057
]
Thierry Delprat commented on NXP-6265:
--------------------------------------
See http://hg.nuxeo.com/nuxeo/nuxeo-features/rev/e17f10129a50
Automation Call can now be x-www-form-urlencoded.
The expecyted body content is :
jsondata={input:XXX, params:{...}, context:{...},documentProperties=YYY }
NB : the actual content should be url encoded !
> Make Automation REST API compatible with OAuth and OpenSocial call
> ------------------------------------------------------------------
>
> Key: NXP-6265
> URL: https://jira.nuxeo.com/browse/NXP-6265
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
> Components: Automation, Dashboard / OpenSocial, Security / Rights
> Affects Versions: 5.4.0.1
> Reporter: Thierry Delprat
> Assignee: Thierry Delprat
> Fix For: 5.4.1
>
>
> OAuth implies that POST requests must be x-www-form-urlencoded
> => need to adapt OAuth filter to handle POST request
> => need to update Automation Server so that we have a compliant MessageReader
> Furthermore Automation uses some additional headers to configure the output.
> OpenSocial does remove all the header except the OAuth headers.
> Even if we can fix this in Nuxeo/Shindig implementation, this will still be
> an issue for almost all OpenSocial containers.
> => must provide an alternate solution based on the POST body content
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.com/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
