Conflict between PrivilegeRegistry and Spec for ServiceRoot

Hi Jeff,

Thank you for the clarification.

Regards,
Elijah

Elijah,

After further discussion with the group, we agreed that adding a new privilege of "NoAuth" to the privilege list was the best approach. That privilege will show up in the Privilege Registry for resources that can be accessed without authentication, but will never appear in a "Role" definition. This prevents the empty array case for ServiceRoot as discussed above. But one additional modification was made to that map - the "Login" privilege will remain, as that is also a valid privilege. We didn't want implementations to reject requests for ServiceRoot (or any other resource that doesn't require authentication) if valid credentials were provided.

So the updated Privilege Registry will have this entry:

"Entity": "ServiceRoot",
"OperationMap": {
"GET": [
{
"Privilege": [
"Login"
]
},
{
"Privilege": [
"NoAuth"
]
}
],
...

The creation of the "NoAuth" privilege and the updated Privilege Registry were both approved by the DMTF Redfish Forum and will appear in the next release of the Redfish Schema bundle and Redfish Registry bundle. Both of those are currently going through the approval and release cycle, but we wanted to get this answer posted without delay.

Jeff