OAuth 1 Signer

This node allows to create OAuth-1-signed HTTP requests.

“OAuth provides a method for clients to access server resources on behalf of a resource owner (such as a different client or an end-user). It also provides a process for end-users to authorize third-party access to their server resources without sharing their credentials (typically, a username and password pair), using user-agent redirections.“ (see RFC5849)

The node itself does not perform any requests – this must be done with a connected “HTTP Retriever” node.

Supply this node with an input table which contains columns for the full request URLs (including query parameters, if they should be sent), (optionally) a column which denotes the HTTP method if different from GET (e.g. POST, etc.), and (optionally) further columns for further parameters from the request’s entity-body, which should be used for creating the signature (column name being the key, cell content the value). The last only applies, if:

1. The request’s entity-body is single-part,
2. The entity-body is encoded as application/x-www-form-urlencoded, and
3. The request’s Content-Type HTTP header is set to application/x-www-form-urlencoded.

The node will append one column called Authorization which contains the created OAuth data. Select this column in the “HTTP Retriever” configuration in the “Headers” tab and make sure to configure the HTTP Retriever with the same data which you used for signing.

This node is implemented according to Twitter’s instructions, but can be used for general OAuth 1.0 signing purposes. More information about OAuth can be found here.