Opened 8 years ago

Closed 5 years ago

Last modified 5 years ago

#8050 closed defect (fixed)

When using oauth for access to api server imagery requiring username/password will not prompt for user name and password

Reported by: ross@… Owned by: team
Priority: normal Milestone: 16.01
Component: Core imagery Version: latest
Keywords: oauth, imagery, tms, wms, http, basic, auth, authentication, https Cc:

Description (last modified by superduck)

I'm using josm otherwise with imagery that requires a username and password. It works correctly with Authentication set to "Use Basic Authentication". However if I set Authentication to "Use OAuth" it will not prompt for a username and password for the imagery and appears to attempt to connect using oauth, resulting in 401 errors for the imagery (TMS service).

Attachments (0)

Change History (9)

comment:1 Changed 8 years ago by Don-vip

Could you please give us your imagery server url? Thanks.

comment:2 Changed 8 years ago by ross@…


This is the imagery url for use in josm preferences TMS.{zoom}/{x}/{y}.png

zoom 18

If you download the following url in josm you be within the imagery area. However you would need a username and password, which I will not post here, to see the imagery

It should be sufficient for testing purposes for this bug as the error
occurs before josm requests username and password.

comment:3 Changed 8 years ago by anonymous

I spent the past 3 days trying to workout why all of the sudden my tms imagery provider is giving me 401s.

This bug still exists today in 5759 when using a tms or wms server over https with basic authentication.

Temp hacky fix: I had to setup a mapproxy server just to hand over the credentials, but for some reason it won't let me zoom past 19.

I inspected its communications with fiddle and no Authorization: Basic <base64> was sent in the request.

comment:4 Changed 8 years ago by anonymous

I have setup OSM via OAuth through the "semi-automatic" setup.

comment:5 Changed 8 years ago by superduck

Comments 3 and 4 are mine.

Last edited 8 years ago by superduck (previous) (diff)

comment:6 Changed 8 years ago by superduck

Component: CoreCore imagery
Description: modified (diff)
Keywords: tms wms http basic auth authentication https added

comment:7 in reply to:  6 Changed 8 years ago by superduck

Replying to superduck:
Description wasn't modified (diff is empty)

comment:8 Changed 5 years ago by simon04

Resolution: fixed
Status: newclosed

In 9313/josm:

fix #8050 - Make OSM API OAuth and imagery HTTP authentication work

Fix: When using OAuth for access to API server, imagery requiring username/password will not prompt for username and password

comment:9 Changed 5 years ago by simon04

Milestone: 16.01

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.