[Backlogmanager] [FIWARE-JIRA] (HELP-9476) [fiware-stackoverflow] Wirecloud FI-Ware Testbed compatibility

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez deleted HELP-9476:
---------------------------------


> [fiware-stackoverflow] Wirecloud FI-Ware Testbed compatibility
> --------------------------------------------------------------
>
>                 Key: HELP-9476
>                 URL: https://jira.fiware.org/browse/HELP-9476
>             Project: Help-Desk
>          Issue Type: Monitor
>            Reporter: Backlog Manager
>              Labels: fiware, fiware-wirecloud
>
> Created question in FIWARE Q/A platform on 04-07-2014 at 15:07
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/24575109/wirecloud-fi-ware-testbed-compatibility
> +Question:+
> Wirecloud FI-Ware Testbed compatibility
> +Description:+
> I was wondering if Wirecloud offers complete support for object storage with FI-WARE Testbed instead of Fi-lab. I have successfully integrated Wirecloud with Testbed and have developed a set of widgets that are able to upload/download files to specific containers in Fi-lab with success. However, the same widgets do not seem to work in Fi-lab, as i get an error 500 when trying to retrieve the auth tokens (also with the well known object-storage-test widget) containing the following response:
> SyntaxError: Unexpected token 
>     at Object.parse (native)
>     at create (/home/fiware/fi-ware-keystone-proxy/controllers/Token.js:343:25)
>     at callbacks (/home/fiware/fi-ware-keystone-proxy/node_modules/express/lib/router/index.js:164:37)
>     at param (/home/fiware/fi-ware-keystone-proxy/node_modules/express/lib/router/index.js:138:11)
>     at pass (/home/fiware/fi-ware-keystone-proxy/node_modules/express/lib/router/index.js:145:5)
>     at Router._dispatch (/home/fiware/fi-ware-keystone-proxy/node_modules/express/lib/router/index.js:173:5)
>     at Object.router (/home/fiware/fi-ware-keystone-proxy/node_modules/express/lib/router/index.js:33:10)
>     at next (/home/fiware/fi-ware-keystone-proxy/node_modules/express/node_modules/connect/lib/proto.js:195:15)
>     at Object.handle (/home/fiware/fi-ware-keystone-proxy/server.js:31:5)
>     at next (/home/fiware/fi-ware-keystone-proxy/node_modules/express/node_modules/connect/lib/proto.js:195:15)
> I noticed that the token provided in the beggining (to start the transaction) is 
> token: Object
> id: "%fiware_token%"
> Any idea regarding what might have gone wrong?



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)