Opened 21 months ago
Closed 19 months ago
#2493 closed defect (wontfix)
Add input field for Name on Manual Keyring Addition form
Reported by: | Reportage | Owned by: | zzz |
---|---|---|---|
Priority: | minor | Milestone: | 0.9.41 |
Component: | apps/console | Version: | 0.9.39 |
Keywords: | Manual Keyring Addition, UX | Cc: | |
Parent Tickets: | Sensitive: | no |
Description
The Manual Keyring Addition form is missing a field for the Name of the service, which results in the encrypted destinations tables having an empty column for the Name. If the name can be automatically pulled from the Tunnel Manager, great, otherwise manual entry is fine.
The name could then also be used to delete an existing key.
Subtickets
Change History (2)
comment:1 Changed 20 months ago by
Milestone: | undecided → 0.9.41 |
---|---|
Owner: | changed from sadie to zzz |
Status: | new → accepted |
comment:2 Changed 19 months ago by
Resolution: | → wontfix |
---|---|
Sensitive: | unset |
Status: | accepted → closed |
The page already did a reverse lookup both for local tunnel nickname, and if not present, in the addressbook. The rework of the page for LS2 brought that code forward. Check boxes were added for deletion of individual entries. The form was also reworked, but I didn't see any reason for a name field, given the reverse lookup already present, and the change to the way deletion works.
This page is going to get reworked or replace shortly as a part of the encrypted LS2 (proposal 123) per-client-auth work.