|
Post by AMI_Felix on May 19, 2022 13:43:49 GMT
Hi, I'm able to see below content via GET /redfish/v1/$metadata:
<edmx:Reference Uri="/redfish/v1/JsonSchemas/AMIManager_v1.xml">
<edmx:Include Namespace="AMIManager"/>
<edmx:Include Namespace="AMIManager.v1_0_0"/>
</edmx:Reference>
<edmx:Reference Uri="/redfish/v1/JsonSchemas/AMIBIOSInventoryCRC_v1.xml">
<edmx:Include Namespace="AMIBIOSInventoryCRC"/>
<edmx:Include Namespace="AMIBIOSInventoryCRC.v1_0_0"/>
</edmx:Reference>
<edmx:Reference Uri="/redfish/v1/JsonSchemas/InventoryCRC_v1.xml">
<edmx:Include Namespace="InventoryCRC"/>
<edmx:Include Namespace="InventoryCRC.v1_0_0"/>
</edmx:Reference>
But I given URI with .xml extension like GET /redfish/v1/JsonSchemas/AMIBIOSInventoryCRC_v1.xml will return 403 forbidden error. Why the URI link exist in $metadata but cannot GET it via Redfish?
Thanks, Felix
|
|
|
Post by mraineri on May 20, 2022 0:46:57 GMT
That sounds like a bug in the implementation. This would need to be reviewed by whoever designed the service you're using.
I would also question the placement of the XML file being under JsonSchemas from a URI perspective since they are not JSON Schemas. The issue may be related; this could be the a case where credentials are required to access any URI at "/redfish/v1/JsonSchemas/{LastSegment}". Regardless though, this would need to be root caused by someone who works on the implementation.
|
|