Modify

Opened 2 years ago

Last modified 17 months ago

#8050 new defect

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:
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 (7)

comment:1 Changed 2 years ago by Don-vip

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

comment:2 Changed 2 years ago by ross@…

Hi,

This is the imagery url for use in josm preferences TMS.

http://mail65.theinternethost.com.au/other/agri/tiles/{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

http://www.openstreetmap.org/?lat=-17.9575&lon=122.237&zoom=14

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

comment:3 Changed 17 months 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 17 months ago by anonymous

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

comment:5 Changed 17 months ago by superduck

Comments 3 and 4 are mine.

Last edited 17 months ago by superduck (previous) (diff)

comment:6 follow-up: Changed 17 months ago by superduck

  • Component changed from Core to Core imagery
  • Description modified (diff)
  • Keywords tms wms http basic auth authentication https added

comment:7 in reply to: ↑ 6 Changed 17 months ago by superduck

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

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as new .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team. Next status will be 'new'.
Next status will be 'needinfo'.The owner will change to ross@theinternethost.com.au
as duplicate The resolution will be set to duplicate. Next status will be 'closed'.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous. Next status will be 'assigned'.
Author


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

 
Note: See TracTickets for help on using tickets.