Project

General

Profile

Bug #25303

Add ability to edit a Certificate

Added by John Smith about 1 year ago. Updated 12 months ago.

Status:
Resolved
Priority:
Nice to have
Assignee:
Nikola Gigic
Category:
Middleware
Target version:
Seen in:
Sprint:
Severity:
New
Backlog Priority:
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Once a certificated is added successfully, it's impossible to edit the certificate (itself, as in its content).
It should be changeable, considering certificates are set to expire every so often and need to be replaced, or even in case of mistake.

Associated revisions

Revision 0492acb4 (diff)
Added by Nikola Gigic about 1 year ago

fix(api/middleware): Unable to change Certificate

Ticket: #25303

Revision af57a2d9 (diff)
Added by Nikola Gigic about 1 year ago

fix(api/middleware): Unable to change Certificate

Ticket: #25303

Revision 55007291 (diff)
Added by Nikola Gigic about 1 year ago

fix(api/middleware): Unable to change Certificate (#313)

Ticket: #25303

Revision 12eb5516 (diff)
Added by Nikola Gigic about 1 year ago

fix(api/middleware): Unable to change Certificate (#313)

Ticket: #25303

Revision 49cf6fa8 (diff)
Added by Dru Lavigne about 1 year ago

Indicate can now edit certificates.
Ticket: #25303

History

#1 Updated by Dru Lavigne about 1 year ago

  • Assignee changed from Release Council to Suraj Ravichandran

Typically one would revoke a certiricate rather than edit it.

Off to Suraj for investigation of this feature.

#2 Updated by John Smith about 1 year ago

Dru Lavigne wrote:

Typically one would revoke a certiricate rather than edit it.

When the certificate expires and a new one is issued with the same CSR, there's no need to replace the private key, and only the certificate is replaced.
Also, mistakes cannot be corrected without removing and inserting a new certificate, which also involves updating other settings (the which-certificate-to-use in httpd menu).

#3 Updated by Suraj Ravichandran about 1 year ago

  • Category changed from 2 to Middleware
  • Status changed from Unscreened to Screened
  • Priority changed from No priority to Nice to have
  • Target version set to 11.2-BETA1

#4 Updated by Dru Lavigne about 1 year ago

  • Assignee changed from Suraj Ravichandran to William Grzybowski

William: please load balance between Vladimir and Nikola.

#5 Updated by William Grzybowski about 1 year ago

  • Status changed from Screened to Unscreened
  • Assignee changed from William Grzybowski to Nikola Gigic

Another one, there is no immediate priority for this.

#6 Updated by Nikola Gigic about 1 year ago

  • Status changed from Unscreened to Screened

#7 Updated by Nikola Gigic about 1 year ago

  • Status changed from Screened to Needs Developer Review

#8 Updated by William Grzybowski about 1 year ago

  • Status changed from Needs Developer Review to Ready For Release

#9 Updated by William Grzybowski about 1 year ago

  • Target version changed from 11.2-BETA1 to 11.1

#10 Updated by Dru Lavigne about 1 year ago

  • Subject changed from Unable to change Certificate to Add ability to edit a Certificate
  • Target version changed from 11.1 to 11.1-BETA1

#11 Updated by Dru Lavigne 12 months ago

  • Status changed from Ready For Release to Resolved

#12 Updated by Bonnie Follweiler 12 months ago

  • Needs QA changed from Yes to No
  • QA Status Test Passes FreeNAS added
  • QA Status deleted (Not Tested)

Also available in: Atom PDF