Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

custom consumer key/secret in twitter node #145

Open
ramajd opened this issue Nov 21, 2015 · 1 comment
Open

custom consumer key/secret in twitter node #145

ramajd opened this issue Nov 21, 2015 · 1 comment

Comments

@ramajd
Copy link

ramajd commented Nov 21, 2015

currently twitter node is using a hard coded consumer key and consumer secret in its node definition,
is it possible to change this node in order to get these parameters from users to allow them use their own generated keys?
maybe its good to use predefined consumer key/secret if user didn't supply its own keys.

@knolleary
Copy link
Member

Copying over what I said on the mailing list...

Yes, that is something we ought to enable.

When we created the nodes for the other web services (https://github.com/node-red/node-red-web-nodes), we decided to require the user to get their own app keys for each service, rather that hardcode in a set as we did with the Twitter node. But we also decided it would be too disruptive to change the Twitter node over to that model entirely.

For some reason it didn't occur to me at the time we ought to update the Twitter node to allow user-defined keys to be provided as an alternative to using the built in keys.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants