Is it possible to add new member to the Enum?

AMI_alvin
Minnow

Posts: 20

Is it possible to add new member to the Enum? Dec 2, 2021 2:44:15 GMT

Quote

Post by AMI_alvin on Dec 2, 2021 2:44:15 GMT

Hi,

Is there any way to add new member for the enum?

For example, Certificate.v1_5_0.json schema defines "CertificateUsageType" enum members :

CertificateUsageType: {

   enum: [

   "User",

   "Web",

   "SSH",

   "Device",

   "Platform",

   "BIOS"

],

But for our BMC certificate usage, it doesn't match any one of the given CertificateUsageType. If we want to add one CertificateUsageType like "TLS", is there any way or oem property support to do this?

Thanks!

jautor
Administrator

Posts: 519

Is it possible to add new member to the Enum? Dec 2, 2021 5:36:41 GMT AMI_alvin likes this

Quote

Post by jautor on Dec 2, 2021 5:36:41 GMT

If the usage is applicable to multiple vendors or implementations, it would certainly be something we would consider adding to the standard enumeration list. If you're a DMTF Redfish Forum member company, you can open an issue for that.

Or for simple feedback items like this, asking here is also sufficient. "TLS" would seem to be covered by "Web", however, isn't it?

Jeff

AMI_alvin
Minnow

Posts: 20

Is it possible to add new member to the Enum? Dec 2, 2021 6:50:16 GMT

Quote

Post by AMI_alvin on Dec 2, 2021 6:50:16 GMT

Hi Jeff,

I checked the description for "Web" :

Web: "This certificate is a web or HTTPS certificate like those used for event destinations."

It seems that "Web" is only for HTTPS(HTTP over TLS), and I think it doesn't conver every TLS usage cases. For my case, the communication is based on TLS, not HTTPS, so the current "CertificateUsageType" cannot convered our case.

So I will open an issue for this, thanks for your reply.

Thank you,
Alvin

mraineri
Administrator

Posts: 1,134

Is it possible to add new member to the Enum? Dec 2, 2021 13:45:45 GMT AMI_alvin likes this

Quote

Post by mraineri on Dec 2, 2021 13:45:45 GMT

I agree that "Web" is strictly for HTTPS (at least at this time). At least when the list was originally proposed, those were the common use cases that came up. As Jeff said, we can certainly add more to the list as new use cases are identified.