|
Post by AMI_Mani on Nov 24, 2018 16:57:04 GMT
Hi All,
As per HI Schema (http://redfish.dmtf.org/schemas/v1/HostInterface.v1_2_0.json), AuthenticationModes attribute is mentioned as writable(readonly as false and copied attribute details at the end of mail). But how user can patch the value, since description mentions authentication modes available on this interface. Assume implementation is supporting both "BasicAuth",
"RedfishSessionAuth" and it will list both values under AuthenticationModes . Do we need to allow the user to change the value to patch as RedfishSessionAuth or BasicAuth to use one mode as HI communication? Is this typo in schema(readonly: false), if so please confirm
AuthenticationModes: {
description: "Indicates the authentication modes available on this interface.",
items: {
$ref: "#/definitions/AuthenticationMode"
},
longDescription: "The value of this property shall be an array consisting of the authentication modes allowed on this interface.",
readonly: false,
type: "array",
},
Thanks, Mani
|
|
|
Post by jautor on Dec 16, 2018 19:13:34 GMT
The only read-write requirement I believe in the entire specification is for the creation of a Session. Otherwise, the Service is not required to provide read-write support on any properties. The schema only specifies the capabilities allowed.
I'll bring this one with the group, but I believe it is correctly defined - the intent was to allow a user (Admin-level most likely) the ability to enable/disable authentication modes of the Host Interface. So that while a Service may support an un-authenticated session from the Host, the user could decide to require authentication for their environment.
Jeff
|
|