Jazz secured request ignores OAuth Authorization header
I sing up with my application to https://jazz2.mycompany.com:9443 using OAuth 1.0a authorization method.
Then when I try to send request to
with "Authorization: OAuth ..." header with all OAuth standart parameters,
Authorization: OAuth
</div>
<div>
realm="http://SERVERNAME/rm",
</div>
<div>
oauth_consumer_key="49cfd21d97cf4808b730f072c902cef7",
</div>
<div>
oauth_signature_method="HMAC-SHA1",
</div>
<div>
oauth_signature="HjgQTj8a%2BK4VrqmaU3yiFa4rQgQ%3D",
</div>
<div>
oauth_timestamp="1378405866",
</div>
<div>
oauth_nonce="e91dd2cca23f429e6e45a049bb856817",
</div>
<div>
oauth_token="1d45c97961754fa4b4813fd9e756c5e9",
</div>
<div>
oauth_version="1.0"'
response is
401 Unauthorized .
But if I send the same OAuth Authorization header parameters as simple request parameters. I get
200 OK response.
Looks like
jazz server somehow ignores header passed Authorization data. Would like to know why? And is there any way to make it work?
|
One answer
The Jazz based version of form based authentication with OAuth uses it's own set of headers.
Comments
Tom Tom2
commented Jun 13 '17, 1:47 p.m.
No I haven't.
What headers Jazz uses for oAuth authentication? Is it possible some how send authenticated requests with standard oAuth headers?
No don't think Jazz support the standard OAuth dance. Once red in a Jazz article that Jazz servers are structured as OAuth Providers, but have their own implementation details. And DNG delegates authentication to JTS and only supports form-based authentication.
Thank you for explanation |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.