Opened 14 years ago

Closed 14 years ago

Last modified 21 months ago

#5100 closed defect (fixed)

Cannot Retrieve OAuth Request Token — at Version 13

Reported by: iovan4o Owned by: team
Priority: critical Milestone:
Component: Core Version: tested
Keywords: OAuth Cc:

Description (last modified by skyper)

I run josm-tested version 3208,
I go to Preferences->Connection Settings->Authentication, select "Use OAuth" and click the "Authorize now" button. In the "Get an Access Token..." dialog I select Semi-automatic procedure. After I click "Retrieve Request Token" button an error dialog appears with the following message:
Retrieving an OAuth Request Token from 'http://www.openstreetmap.org/oauth/request_token' failed.
In the console there is the following exception:

org.openstreetmap.josm.gui.oauth.OsmOAuthAuthorizationException: oauth.signpost.exception.OAuthNotAuthorizedException:
Authorization failed (server replied with a 401). This can happen if the consumer key was not correct or the signatures did not match.
        at org.openstreetmap.josm.gui.oauth.OsmOAuthAuthorizationClient.getRequestToken(OsmOAuthAuthorizationClient.java:141)
        at org.openstreetmap.josm.gui.oauth.RetrieveRequestTokenTask.realRun(RetrieveRequestTokenTask.java:79)
        at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:83)
        at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:129)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: oauth.signpost.exception.OAuthNotAuthorizedException: Authorization failed (server replied with a 401).
This can happen if the consumer key was not correct or the signatures did not match.
        at oauth.signpost.basic.DefaultOAuthProvider.retrieveToken(DefaultOAuthProvider.java:143)
        at oauth.signpost.basic.DefaultOAuthProvider.retrieveRequestToken(DefaultOAuthProvider.java:79)
        at org.openstreetmap.josm.gui.oauth.OsmOAuthAuthorizationClient.getRequestToken(OsmOAuthAuthorizationClient.java:132)
        ... 9 more

Regards,
Ivan

Change History (13)

comment:1 by toje@…, 14 years ago

Keywords: OAuth added
Version: tested

I am also getting this error. The core problem seems to be that the OSM OAuth server returns a 401 error code:

org.openstreetmap.josm.gui.oauth.OsmOAuthAuthorizationException: oauth.signpost.exception.OAuthCommunicationException: Communication with the service provider failed: Server returned HTTP response code: 401 for URL: http://www.openstreetmap.org/oauth/request_token

Could it be that there's something broken with the way JOSM generates it's OAuth request token?

A working OAuth would be very much appreciated by me, as I usually don't like sending any authentication data in the clear (for hopefully obvious reasons).

Greetings from Stuttgart,

=ToJe=

comment:2 by Sellerhäuser, 14 years ago

Cc: josm-trac@… added

Same here: Fully automatic doens't work at all, semi-automatic returns above mentioned error code 401
used manual procedure, tried to test the Access Token returns error:

Failed to access the OSM server 'http://api.openstreetmap.org/api' with the Access Token 'http://api.openstreetmap.org/api'. ...

It seems that there is an error with some variables, the server address shouldn't be the Access Token

comment:3 by Sellerhäuser, 14 years ago

Tested again and it works for me ... (Version 3376)
Haven't changed anything since the last comment

comment:4 by Sellerhäuser, 14 years ago

Cc: josm-trac@… removed

Tested again with different systems (Windows, Linux), requested new token, testing token access and it works on all of them

seems not to be an error of JOSM

comment:5 by stoecker, 14 years ago

Resolution: irreproducible
Status: newclosed

comment:6 by bastiK, 14 years ago

Resolution: irreproducible
Status: closedreopened

@Stoecker can you request a token?

It is still broken for me.

comment:7 by stoecker, 14 years ago

Yes. Had no problems when I tried.

comment:8 by stoecker, 14 years ago

Ah, rechecked and is broken in latest. Probably caused by the latest signpost-update.

comment:9 by stoecker, 14 years ago

Resolution: fixed
Status: reopenedclosed

(In [3494]) fix #5100 - OAuth failing

comment:10 by stoecker, 14 years ago

Ticket #5392 has been marked as a duplicate of this ticket.

comment:12 by anonymous, 21 months ago

failing in version 17423

in reply to:  12 comment:13 by skyper, 21 months ago

Description: modified (diff)

Replying to anonymous:

failing in version 17423

Commenting on an ancient, closed ticket does not help.
There are still some problems with open tickets: query
Some significant changes were made in r17972, so please, update JOSM.

Note: See TracTickets for help on using tickets.