For OAuth 1.0 or 1.0a (OAuth Core 1.0a):
-
Use the Authorization scheme “OAuth”. (“Bearer” is for OAuth 2.0.)
-
Pass parameters in one of three methods, in order of decreasing preference:
i) In the HTTP Authorization header as defined in OAuth HTTP Authorization Scheme.
ii) As the HTTP POST request body with a content-type of application/x-www-form-urlencoded.
iii) Added to the URLs in the query part (as defined by [RFC3986] section 3).
The spec provides an example:
Authorization: OAuth realm="http://sp.example.com/",
oauth_consumer_key="0685bd9184jfhq22",
oauth_token="ad180jjd733klru7",
oauth_signature_method="HMAC-SHA1",
oauth_signature="wOJIO9A2W5mFwDgiDvZbTSMK%2FPY%3D",
oauth_timestamp="137131200",
oauth_nonce="4572616e48616d6d65724c61686176",
oauth_version="1.0"
IS does not directly support OAuth 1.0. If you populate the “auth” structure in the inputs to pub.client:http, it will not set the Authorization scheme to “OAuth”. Instead, you can either explicitly create an Authorization header as above and map in into the “headers” input to the pub.client:http, or you can put these parameters in the body of the request or as URL query parameters. See the pub.client:http documentation on how to do this. You may want to check with the owner of the remote server learn which formats they support.
#API-Portal#API-Gateway#API-Management#webMethods