Your message dated Mon, 14 Oct 2024 14:55:45 +0200
with message-id <[email protected]>
and subject line Re: Bug#1085091: josm: OAuth token request process does not
work
has caused the Debian Bug report #1085091,
regarding josm: OAuth token request process does not work
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1085091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085091
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: josm
Version: 0.0.svn18646+dfsg-1
Severity: important
I have been using josm for many years, and when it was et up it used basic auth
(name+password).
That functionality has been withdrawn and now oauth is supposed to be used.
However I am unable to get this to work, and it seems that this versionof josm
is not asking on the right URLs.
If I use the 'Authorise now (fully automatic)' button I get:
"The automatic process for retrieving an OAuth Access Token from the OSM server
failed. Please try again or choose another kind of authorisation process, i.e.
semi-automatic or manual authorisation."
after clicking on the 'Authorise now' button.
If I use the 'Authorise now (semi-automatic)' button, in step 1 when I click on
'retreive request token' it says: "Retrieving an OAuth Request Token from
'https://www.openstreetmap.org/oauth/request_token' failed.
And indeed if I go manually to
"https://www.openstreetmap.org/oauth/request_token"; I get a 404. So I presume
some different URL should be used now?
If I click on the help button in that dialog I get "The page En_GB:Help/OAuth
does not exist. You can create it here."
The text above the 'Retreive Request Token' button says:
"Please click on Retrieve Request Token to retrieve an OAuth Request Token from
''."
which suggests there there is an unset value that should be appearing in
between those single quoes?
It's not clear how to fix this. I presume the software is now simply
too old for the website. Or more accurately the website has not kept
the API going long enough for the software still in use in stable
versions, which is poor practise IMHO. Would it really be that hard to
keep it working until there was a new stable version that knew about
whatever the new URLs are?
This is quite a serious problem because JOSM without the ability to
upload to OSM isn't really very useful.
--
Wookey
--- End Message ---
--- Begin Message ---
On 10/14/24 2:43 PM, Wookey wrote:
I have been using josm for many years, and when it was et up it used basic auth
(name+password).
That functionality has been withdrawn and now oauth is supposed to be used.
You need to use OAuth 2.0 now:
https://josm.openstreetmap.de/wiki/Help/Preferences/Connection#oauth2
This is available in the version in bookworm-backports, as OAuth2 support was
introduced in 18650:
https://josm.openstreetmap.de/ticket/20768#comment:53
And support for OAuth 1.0a was removed in 18991:
https://josm.openstreetmap.de/ticket/22810#comment:25
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
