Skip to contentSkip to conversation

API authentication

DISCUSSION Brad Bishop 2 participants 3 messages Mar 18, 2019 – Mar 20, 2019

lore
Share & tools
lore
#0 lore raw

I am looking for ideas on how to implement a mechanism to restrict access to specific methods of a service/API (e.g. Redfish).

This would be orthogonal to role-based authorization - e.g. the authorization would be provided by someone other than the system administrator - e.g. the system manufacturer.

I think I want OAuth for this with these definitions:

resource owner: system manufacturer
client: any user of the API (could be application specific but not required)
resource: data flowing over the API being authorized

Could the system manufacturer authorize clients on non-internet connected BMCs?

Is there a better way to go about this?

Does anyone have any experience with something like this? I would love to be pointed to further reading, code, or just your thoughts in general.

thx - Brad

#1 lore raw
Quoted 6 lines · Brad Bishop

I am looking for ideas on how to implement a mechanism to restrict access to specific methods of a service/API (e.g. Redfish).

This would be orthogonal to role-based authorization - e.g. the authorization would be provided by someone other than the system administrator - e.g. the system manufacturer.

Is this a followup to the March 4 OpenBMC Community call? https://github.com/openbmc/openbmc/wiki/Weekly-Community-Telecon

My understanding is that we would design and code the BMC with functions for things like manufacturing test and specialized diagnostics ... functions which could harm the device, etc. So we want the functions to be present for manufacturing test and service calls, but locked out for all other users. Is that what this mechanism is for?

- Joseph

Quoted 14 lines

I think I want OAuth for this with these definitions:

resource owner: system manufacturer
client: any user of the API (could be application specific but not required)
resource: data flowing over the API being authorized

Could the system manufacturer authorize clients on non-internet connected BMCs?

Is there a better way to go about this?

Does anyone have any experience with something like this? I would love to be pointed to further reading, code, or just your thoughts in general.

thx - Brad

#2 lore raw
Quoted 11 lines · Joseph Reynolds
Quoted 6 lines · Brad Bishop

I am looking for ideas on how to implement a mechanism to restrict access to specific methods of a service/API (e.g. Redfish).

This would be orthogonal to role-based authorization - e.g. the authorization would be provided by someone other than the system administrator - e.g. the system manufacturer.

Is this a followup to the March 4 OpenBMC Community call? https://github.com/openbmc/openbmc/wiki/Weekly-Community-Telecon

My understanding is that we would design and code the BMC with functions for things like manufacturing test and specialized diagnostics ... functions which could harm the device, etc. So we want the functions to be present for manufacturing test and service calls, but locked out for all other users. Is that what this mechanism is for?

I hadn't thought of mfg mode commands as a use case for this but on the surface it does seem to be a match.