search

watson-developer-cloud / node-red-node-watson

A collection of nodes for the IBM Watson services
Apache License 2.0
82 stars 86 forks source link

Loaded 15.2 node-red and Watson conversation service no longer as username password fields to config #222

Closed dennisnotojr closed 7 years ago

dennisnotojr commented 7 years ago

Testing the latest node-red, watson nodes, etc. Noticed that all watson services have username and password but watson conversation service only has workspace_id? How do you set the username/password for the service? Works find in my 14.4 build, and 15.1 build of node-red.

Thanks, Den

chughts commented 7 years ago

All the Nodes work the same, they all ask for credentials, unless the credentials are automatically found because the service is bound to the node-red application.

dennisnotojr commented 7 years ago

Dude, that does not address the problem. you can not put in the credentials to the watson conversation service which the latest release. This is a bug! Picture attached. Username and password fields are gone!

wcs

dennisnotojr commented 7 years ago

All other watson nodes have the username/password fields. Please fix immediately or route to the ones can address.

dennisnotojr commented 7 years ago

Here's what it looked like in the 15.1 release of node-red which is correct. wcs2

chughts commented 7 years ago

This is a Bluemix instance that I created today, and didn't bind in Conversation.

screen shot 2016-11-29 at 14 14 21
chughts commented 7 years ago

What is the name of your Node-RED application?

dennisnotojr commented 7 years ago

could this be an issue with the boiler plate Node-Red Starter title. That is what I used to create my new instance? Doesn't make any sense.

dennisnotojr commented 7 years ago

Try it yourself.

chughts commented 7 years ago

Most likely to be related to the name of your node-red instance. The cloudant database that gets created will match that name. That means that when the vcap module looks for the conversation setting it finds the cloudant one. This is a known problem with all the services, not just conversation.

dennisnotojr commented 7 years ago

Let me try a different name

dennisnotojr commented 7 years ago

can the app name and host name be the same?

chughts commented 7 years ago

App name and host name can be the same.

dennisnotojr commented 7 years ago

Well your hunch was correct. Used a different name and the username/password is now present.

Weird - the name I used before "UCG" didn't work, but "NodeRed-V3" did? Hmm.