Watson Workspace will no longer be available after February 28, 2019. Learn more.

Developers

Registering a callback url, gives error ( watsonwork-sentiment )

Comments

3 comments

  • Avatar
    Miguel Estrada

    Hello,  wondering if you are using latest code from the sample.  It was updated on Nov 8, 2016 to correct a problem which could result in the error you are experiencing.  

    Let me know if you are indeed using latest code and still experiencing the problem.  Also, see the log in bluemix and what it indicates.  

  • Avatar
    Dipendu Ganguly

    Hello, I am using the latest code. I get the following error on BlueMix

    2016-11-10T23:45:47.685-0600

    [App/0]

    out

    {"type":"verification","challenge":"1ziddhycwg1blq8zf8x6xwuiruuvcgj9"}
    2016-11-10T23:45:47.685-0600
    [App/0]
    out
    ERROR: Cannot verify caller! -------------
    2016-11-10T23:45:47.689-0600

    [RTR/0]

    out

    watsonworkspace-sentiment.tcs.us-south.mybluemix.net - [11/11/2016:05:45:47.674 +0000] "POST /webhook_callback/ HTTP/1.1" 200 70 0 "-" "Apache-HttpClient/4.5.2 (Java/1.8.0)" 169.55.41.40:53264 x_forwarded_for:"54.162.229.49" x_forwarded_proto:"https" vcap_request_id:e7f40ae0-d46e-4cd7-7434-0310c035fcde response_time:0.014060114 app_id:1b331cf8-55d0-440a-9429-43739ee7ec80 x_global_transaction_id:"88729449"
  • Avatar
    Miguel Estrada

    Ok.  that is helpful.  Can you verify that the webhook secret being used in the environment for the bluemix App (Steps 7.v and 8 in the readme) match the application registration that you are trying to enable a webhook for?

    You can see at https://github.com/watsonwork/watsonwork-sentiment/blob/master/app.js#L215 the process being used to verify that the secret used by the app in registration matches the one being used by the app in bluemix runtime.  

Please sign in to leave a comment.