White Papers
12 Implementation of the DMTF Redfish API on Dell EMC PowerEdge Servers
Or, more graphically represented as:
Note that the API is best navigated starting from the root as some portions of an API path can vary depending
upon the server hardware configuration. For example, the “RAID.Integrated.1-1” Sub-item in the preceding
example may be different when another type of RAID controller is installed in the managed server.
2.6.2 Redfish operations
In Redfish, HTTP methods implement the operations of a RESTful API. This allows the user to specify the
type of request being made. It adheres to a standard CRUD (Create, Retrieve, Update, and Delete) format.
Depending on the desired result, a user can issue the following types of commands:
GET View data
POST Create resources or use actions
PATCH Change one or more properties on a resource
DELETE Remove a resource
Note: In the current implementation, HEAD and PUT operations are not supported for Redfish URIs.
Creation and removal of data are limited depending on the management characteristics of the resource being
targeted. Generally, viewing and changing settings will be more common.
2.6.3 Authentication
Depending upon the sensitivity of a given resource, Redfish clients will be required to authenticate their
access. The required credentials and supported forms of authentication are determined by the platform being
managed. In the case of iDRAC, authentication is supported using local iDRAC credentials or any of the other
supported authentication methods, such as LDAP and Active Directory.
Access to iDRAC data is allowed by authenticated and authorized users only, except as noted below.
Authentication is achieved using a subset of the common HTTP headers supported by a Redfish service – in
particular, the X-Auth-Token header. More details on authentication are provided in the “Session
Management” section of the Redfish specification.
Authorization covers both user privilege and license authorization. Note that iDRAC Redfish support does not
require any special or separate licensing. The following table details the authentication and authorization
required for each iDRAC Redfish action: