Thursday, 1 September 2011

Browse » Home » » » » OAuth after Initial Configuration Does Not Work

OAuth after Initial Configuration Does Not Work

Symptoms

While requesting content such as gadgets to be served over OAuth similar warnings are recoded in atlassian-jira.log log file:
2010-09-02 09:21:30,434 http-8081-2 WARN jbond 561x2193x6 h5pd0p  /plugins/servlet/gadgets/makeRequest [http.impl.client.DefaultRequestDirector]  Authentication error: Unable to respond to any of these challenges: {oauth=WWW-Authenticate: OAuth realm="http%3A%2F%2Fbamboo", oauth_problem="token_rejected"}
2010-09-02 09:21:30,742 http-8081-8 WARN jbond 561x2196x6 h5pd0p  /plugins/servlet/gadgets/makeRequest [http.impl.client.DefaultRequestDirector] Authentication error: Unable to respond to any of these challenges: {oauth=WWW-Authenticate: OAuth realm="http%3A%2F%2Fbamboo", oauth_problem="token_rejected"}

Cause

OAuth provider doesn't recognise the consumer as the valid and authorised consumer of its service. In most cases problem observed, if the consumer application is hosted behind Apache HTTPD.

Resolution

Ensure that the front-end Apache HTTPD is configured with the ProxyPreserveHost directive set to ON
Advertisement:

No comments:

Post a Comment

Note: only a member of this blog may post a comment.