Modify ↓

Ticket #3112 (closed enhancement: fixed)

Opened 3 years ago

Last modified 2 years ago

[PATCH] hook for new plugin (native password manager)

Reported by: bastiK Owned by: team
Priority: major Component: Core
Version: latest Keywords:
Cc:

Description

The patch moves the osm-password related code to a central static object. This allowes the upcoming plugin for gnomekeyring and KWallet support to provide its own password handling backend. So far this shouldn't change any visible behaviour.

Attachments

npm_patch Download (16.5 KB) - added by bastiK 3 years ago.
npm_patch_r1953 Download (17.4 KB) - added by bastiK 3 years ago.
npm_add_osm_server Download (11.5 KB) - added by bastiK 2 years ago.
make not only password and username part of credentials management, but also the osm server url

Change History

Changed 3 years ago by bastiK

comment:1 Changed 3 years ago by stoecker

  • Owner changed from team to bastiK
  • Status changed from new to needinfo

The code got a bit out of sync. Could you please update it to current SVN.

Changed 3 years ago by bastiK

comment:2 Changed 3 years ago by bastiK

sure

comment:3 Changed 3 years ago by stoecker

  • Status changed from needinfo to closed
  • Resolution set to fixed

(In [1955]) close #3112 - patch by bastiK - rework username/password handling to allow password hooks

comment:4 Changed 3 years ago by stoecker

One note regarding future extensions - Handling the server URL in the password mechanism may be a good idea as well, so different passwords could be managed for test and development servers.

Also the openstreetbugs plugin needs password management :-)

comment:5 Changed 2 years ago by bastiK

  • Status changed from closed to reopened
  • Resolution fixed deleted

You can have two .josm folders and run

$ java -Djosm.home=~/.josm_dev -jar josm-custom.jar

Isn't this more straightforward than complicated GUI?

And for openstreetbugs: I couldn't find anything like registration or so. Maybe this is going to change?

comment:6 Changed 2 years ago by stoecker

  • Owner changed from bastiK to team
  • Status changed from reopened to new
  • Summary changed from [PATCH] hook for new plugin (native password manager) to hook for new plugin (native password manager)

I don't know what is best. But password managers can manage different password sets, so it seems a sensible idea to me :-)

Changed 2 years ago by bastiK

make not only password and username part of credentials management, but also the osm server url

comment:7 Changed 2 years ago by bastiK

Ok, in one way or another it might be a good idea to include the server url.

Here we go.

comment:8 Changed 2 years ago by stoecker

  • Summary changed from hook for new plugin (native password manager) to [PATCH] hook for new plugin (native password manager)

comment:9 Changed 2 years ago by stoecker

  • Status changed from new to closed
  • Resolution set to fixed

(In [2015]) fixed #3112 - patch by bastiK - cleanup password hook

View ↑

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'reopened'
Author


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

Attachments ↑
 
Note: See TracTickets for help on using tickets.