White Papers

23 Implementation of the DMTF Redfish API on Dell EMC PowerEdge Servers

3.3.10 Update / modify iDRAC user account

The iDRAC has pre-defined slots for internal user accounts. To modify an account, a PATCH action is used

rather than a POST. “RoleId” is used to specify the type of access permissions to be granted to the user; in

this case, the Operator role is used.

import requests

import json

url = 'https://<iDRAC

IP>/redfish/v1/Managers/iDRAC.Embedded.1/Accounts/<Account-id>'

plUserName = {'UserName': 'user03'}

plPass = {'Password': 'calvin'}

plRoleId = {'RoleId': 'Operator'}

headers = {'content-type': 'application/json'}

for payload in plUserName,plPass,plRoleId:

response = requests.patch(url, data=json.dumps(payload), headers=headers,

verify=False, auth=('root','calvin'))

Note: You can configure up to 16 local users in iDRAC with specific access permissions. Before you create

an iDRAC user, verify if any current users exist. You can set user names, passwords, and roles with the

privileges for these users. User 1 is reserved for the IPMI anonymous user and you cannot change this

configuration. By default, User 2 is the “root” user.

Note: iDRAC local users are deleted by setting the user name to NULL.

3.3.11 Redfish 2016 for 12

, 13

and 14

generation PowerEdge servers

PowerEdge 12

, 13

, and 14

generation servers support Redfish 2016 standard APIs including:

 BIOS configuration including set attributes, change boot order, and enable/disable boot device state

 Secure boot configuration

 iDRAC configuration (iDRAC9 only; for iDRAC7 and iDRAC8, use SCP operations to configure

iDRAC)

 Firmware inventory and update

 Storage and networking inventory and configuration

 Memory inventory and statistics

These features are supported on iDRAC7 iDRAC8 firmware versions 2.60.60.60 or later, and iDRAC9

firmware versions 3.18.18.18 or later.

In addition to the standard Redfish APIs, the iDRAC RESTful API includes OEM extensions for Server

Configuration Profiles (SCP) support including:

 RESTful server configuration using an SCP file