How to Show Oem Property in Links - CertificateLocation

abiramisekar
Minnow

Posts: 10

How to Show Oem Property in Links - CertificateLocation Aug 13, 2021 15:24:06 GMT

Quote

Post by abiramisekar on Aug 13, 2021 15:24:06 GMT

Hi,

The Response for CertificateLocation is as below,

{

    "@odata.context": "/redfish/v1/$metadata#CertificateLocations.CertificateLocations",

    "@odata.etag": "\"1628785805\"",

    "@odata.id": "/redfish/v1/CertificateService/CertificateLocations",

    "@odata.type": "#CertificateLocations.v1_0_2.CertificateLocations",

    "Description": "Certificate Locations",

    "Id": "CertificateLocations",

    "Links": {

        "Certificates": [

            {

                "@odata.id": "/redfish/v1/Managers/Self/NetworkProtocol/HTTPS/Certificates/1"

            },

            {

                "@odata.id": "/redfish/v1/EventService/Oem/XXX/SMTP/Certificates/1"

            },

            {

                "@odata.id": "/redfish/v1/EventService/Oem/XXX/SMTP/Certificates/2"

            }

        ],

        "Certificates@odata.count": 3

    },

    "Name": "Certificate Locations"

}

When on running validator tool to check schema compliance,

getting below error,

ERROR - Links.Certificates[0]: Linked resource reports version #Certificate.v1_2_1.Certificate not in Schema localFile:./schemas/Certificate_v1.xml

ERROR - Schema of target /redfish/v1/EventService/Oem/XXX/SMTP/Certificates/1 not referenced in current resource, concluding type #AMISMTPCertificate.v1_0_0.XXXSMTPCertificate is not of expected type Collection(Certificate.Certificate)

ERROR - Links.Certificates[1]: Could not get schema file for Entity check

ERROR - Schema of target /redfish/v1/EventService/Oem/XXX/SMTP/Certificates/2 not referenced in current resource, concluding type #AMISMTPCertificate.v1_0_0.XXXSMTPCertificate is not of expected type Collection(Certificate.Certificate)

ERROR - Links.Certificates[2]: Could not get schema file for Entity check

I checked the CertificateLocations Schema, the Link property could have Oem property
redfish.dmtf.org/schemas/v1/CertificateLocations.v1_0_2.json

Please confirm the format of Oem URI in Link Property,

1. "Links -> Oem -> XXX -> Links -> odata.id of OEM"
2. "Links -> Oem -> XXX -> odata.id of OEM"

which would be the correct format .
Please Clarify.

Thank You,
Abirami S

Last Edit: Aug 16, 2021 5:53:21 GMT by abiramisekar

mraineri
Administrator

Posts: 1,048

How to Show Oem Property in Links - CertificateLocation Aug 13, 2021 15:40:52 GMT

Quote

Post by mraineri on Aug 13, 2021 15:40:52 GMT

From the tool's output, it looks like "/redfish/v1/EventService/Oem/Ami/SMTP/Certificates/2" and "/redfish/v1/EventService/Oem/Ami/SMTP/Certificates/1" are NOT Certificate resources (they appear to be a resource called "AMISMTPCertificate"). This is an illegal usage of the link.

If you have an OEM representation of a certificate that does not conform to the Redfish Certificate resource, then you cannot use it inside of the "Certificates" array inside of the CertificateLocation resource. You will need to create an "Oem" property inside of CertificateLocations to reference your OEM resources. Whether you do this inside of "Links" versus at the root of the resource is really going to depend on what it is these OEM resources represent and how you use them.

Last Edit: Aug 13, 2021 15:44:46 GMT by mraineri

jautor
Administrator

Posts: 502

How to Show Oem Property in Links - CertificateLocation Aug 13, 2021 16:09:27 GMT

Quote

Post by jautor on Aug 13, 2021 16:09:27 GMT

I'm curious why there even needs to be an "OEM" resource instead of just using the standard schema for an EventDestination for an SMTP target? EventDestination has "Protocol" with SMTP as a supported enumeration, the "Destination" can have a value like: "SMTP://user@contoso.com", and there is a "Certificates" collection.

If there's something missing from the standard Event Destination (Event Subscriber, email target) schema, we should get it added to the schema, as email is obviously a popular method of sending events...

Can you tell us what is in that OEM resource that isn't covered by EventDestination?

Jeff

abiramisekar
Minnow

Posts: 10

How to Show Oem Property in Links - CertificateLocation Aug 13, 2021 16:27:16 GMT

Quote

Post by abiramisekar on Aug 13, 2021 16:27:16 GMT

Hi,

"/redfish/v1/EventService/Oem/XXX/SMTP/Certificates/2" and "/redfish/v1/EventService/Oem/xxx/SMTP/Certificates/1" are XXXSMTPCertificate URI
NOT Certificate resources

Inorder to show this odata.id (/redfish/v1/EventService/Oem/XXX/SMTP/Certificates/2) in
CertificateLocation-->Links , how we need to mention?

Please suggest.

With Regards,
Abirami S

Last Edit: Aug 16, 2021 5:54:14 GMT by abiramisekar

mraineri
Administrator

Posts: 1,048

How to Show Oem Property in Links - CertificateLocation Aug 16, 2021 14:44:30 GMT

Quote

Post by mraineri on Aug 16, 2021 14:44:30 GMT

You will need to create an "Oem" property inside of CertificateLocations to reference your OEM resources. Whether you do this inside of "Links" versus at the root of the resource is really going to depend on what it is these OEM resources represent and how you use them. The "Oem" property is available in every resource at the root of the resource as well as within any "Links" properties.