DOORS Next Generation 5.0 scripting
I am trying to use the sample integration for DNG to Evernote hosted on JazzHub - https://hub.jazz.net/project/steven_wood/dng_evernote/overview
I can perform OAuth to Evernote sandbox if I use the widget hosted at https://dng-evernote.ng.bluemix.net/evernote.xml but not running in my own set up.
I have downloaded the code, run 'npm install' to install the required node modules. I then start the app.js by running 'node app.js' and get the response 'Listening on port 3000' so that appears to be working.
I then add the open social widget to my local copy hosted in https://myserver:myport/extensions. When I click on the link to connect to Evernote I get an error message that says 'The requested resource is not available'. The page opens at https://myserver:myport/oauth?user=Neal Middlemore.
This doesn't happen on the hosted application. Any ideas what could be wrong?
The actual import in to a Module isn't working on my system from the hosted widget. I get a message that says 'The resource 'module name' has been concurrently modified, do you want to overwrite the resource with your changes?' It doesn't matter which option I choose, I don't get the import.
Thanks
Neal
|
Accepted answer
Hi Neal,
That is odd. So if i understand you correctly you're saying that the "Click here to authenticate" link is pointing at the wrong place ? The widgets use an HTML <base> tag which sets the base URL to the place the widget came from. This means if i load the widget from http://localhost:3000/evernote.xml then that link should resolve to http://localhost:3000/oauth I'm not sure what you meant by this : I then add the open social widget to my local copy hosted in https://myserver:myport/extensions.To be clear - you do not need to put anything under your tomcat folder for this stuff - the Node server serves the XML as well, so the URL you want to use to add the extension to the UI is : http://localhost:3000/evernote.xml Cheers, Steve. Neal Middlemore selected this answer as the correct answer
Comments Thanks Steve, adding it from the running application rather than the extensions folder was the bit I was missing! |
One other answer
|
Hi Neal,
Does the popup asking you to authenticate appear in your local env ? If not maybe the popup is being blocked, but I reckon you would have spotted this. When hosting the gadget locally are you using http rather than https ? In which case you may need to tell FF to allow mixed content by clicking on the shield at the left of the URL. If you go paste the URL : https://myserver:myport/oauth?user=Neal Middlemore what do you see ? This is supposed to redirect you to the Evernote OAuth page. I have seen the error with the concurrent modification as well - i'll take a look at this when I'm back in the office and open a WI. Thanks, Steve. Comments Hi Steve,
When I use https://doors.ng.int:9443/oauth?user=Neal Middlemore I get the resource not available message. I played around with the URLs and http://doors.ng.int:3000/oauth?user=Neal Middlemore works and brings up the evernote authentication, I tried it with https but it returns an SSL error.
Obviously the link in the widget is using the hostname to connect which is https://doors.ng.int:9443. Is this coming from req.headers,host in the client.getRequestToken in app.js?
Cheers
Neal |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
The issue with the 409 is caused by issuing the createArtifact command before waiting on the save event to fire. I've updated the script on jazz hub so if you do a git pull you should no longer get that message - let me know if you still do.
It's good we can workaround that 409 in the script, but going forward i'll fix the API so that the callback for createArtifact does not fire until the web client has had a chance to make sure it has update the version of the module it is showing.