openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gunnar Mills <gmills@linux.vnet.ibm.com>
To: "Mohammed.Habeeb ISV" <mohammed.habeeb@inventec.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: devenrao@in.ibm.com, ojayanth@in.ibm.com
Subject: Re: No option to delete SSL certificates
Date: Fri, 5 Mar 2021 10:42:43 -0700	[thread overview]
Message-ID: <6fafb378-5de7-74e3-4fef-17cb93d61c41@linux.vnet.ibm.com> (raw)
In-Reply-To: <PS2PR02MB35414D7358C4248DF668A4E790969@PS2PR02MB3541.apcprd02.prod.outlook.com>

On 3/4/2021 8:52 PM, Mohammed.Habeeb ISV wrote:
> In webui-vue , SSL certificates has only replace option. Delete button 
> is greyed out.
> 
> Is there any reason for not providing delete option?

Looking at the code, I believe the only certificate that can be deleted 
in bmcweb is the Trust Store Certificate
https://github.com/openbmc/bmcweb/blob/feaf15005555a3099c7f22a7e3d16c99ccb40e72/redfish-core/lib/certificate_service.hpp#L1347

And this is reflected in the webui-vue code:
https://github.com/openbmc/webui-vue/blob/4da9495925d601bb4edfb8b007d5b54792b7491b/src/views/AccessControl/SslCertificates/SslCertificates.vue#L183

I am not sure if there is a reason for not supporting deleting other 
certificates or just no one has done the work.
https://github.com/openbmc/bmcweb/commit/07a602993f1007b0b0b764bdb3f14f302a8d2e26

Thanks,
Gunnar

  reply	other threads:[~2021-03-05 17:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05  3:52 No option to delete SSL certificates Mohammed.Habeeb ISV
2021-03-05 17:42 ` Gunnar Mills [this message]
2021-03-05 17:52   ` Ed Tanous
2021-03-05 18:22     ` Mohammed.Habeeb ISV
2021-03-05 18:41   ` Milton Miller II
2021-03-05 20:28     ` Ed Tanous
2021-03-05 23:24       ` Derick Montague
2021-03-06  5:03         ` Jayanth Othayoth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6fafb378-5de7-74e3-4fef-17cb93d61c41@linux.vnet.ibm.com \
    --to=gmills@linux.vnet.ibm.com \
    --cc=devenrao@in.ibm.com \
    --cc=mohammed.habeeb@inventec.com \
    --cc=ojayanth@in.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).