Set User Access
更新时间： 2026/08/06
在Gitcode上查看源码Set User Access
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
Set the BMC user access permission.
Privilege
UserMgnt
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | App 06h |
| CMD | 43h |
| 1 | [7]-0b=do not change any of the following bits in this byte 1b=enable changing the following bits in this byte [6]-User Restricted to Callback 0b=User Privilege Limit is determined by the User Privilege Limit parameter, below, for both callback and non-callback connections 1b=User Privilege Limit is determined by the User Privilege Limit parameter for callback connections, but is restricted to Callback level for non-callback connections. Thus, a user can only initiate a Callback when they 'call in' to the BMC, but once the callback connection has been made, the user could potentially establish a session as an Operator [5]-User Link authentication enable/disable (used to enable whether this user's name and password information will be used for link authentication, e.g. PPP CHAP) for the given channel. Link authentication itself is a global setting for the channel and is enabled/disabled via the serial/modem configuration parameters 0b=disable user for link authentication 1b=enable user for link authentication [4]-User IPMI Messaging enable/disable (used to enable/disable whether this user's name and password information will be used for IPMI Messaging. In this case, "IPMI Messaging" refers to the ability to execute generic IPMI commands that are not associated with a particular payload type. For example, if IPMI Messaging is disabled for a user, but that user is enabled for activating the SOL payload type, then IPMI commands associated with SOL and session management, such as Get SOL Configuration Parameters and Close Session are available, but generic IPMI commands such as Get SEL Time are unavailable) 0b=disable user for IPMI Messaging 1b=enable user for IPMI Messaging [3:0]-Channel Number CAUTION: This command is used to set rights in inband mode. The corresponding channel number must be specified. |
| 2 | User ID [7:6]-reserved [5:0]-User ID. 000000b=reserved |
| 3 | User Limits [7:4]-reserved [3:0]-User Privilege Limit. (Determines the maximum privilege level that the user is allowed to switch to on the specified channel) 0h=reserved 1h=Callback 2h=User 3h=Operator 4h=Administrator 5h=OEM Proprietary Fh=NO ACCESS |
| (4) | User Session Limit. (Optional) Sets how many simultaneous sessions can be activated with the username associated with this user. If not supported, the username can be used to activate as many simultaneous sessions as the implementation supports Return a CCh 'invalid data field' error completion code if an attempt is made to set a non-zero value in this field, but the option is not supported [7:4]-reserved [3:0]-User simultaneous session limit. 1-based 0h=only limited by the implementations overall support for simultaneous sessions |
Response Information
| Byte | Data Field |
|---|---|
| 1 | Completion Code Note: an implementation will not return an error completion code if the user access level is set higher than the privilege limit for a given channel. If it is desired to bring attention to this condition, it is up to software to check the channel privilege limits set using the Set Channel Access command and provide notification of any mismatch |
Command Example
Set the BMC user access permission.
Request:
bash
ipmitool raw 0x06 0x43 0xF1 0x03 0x04 0x01Response:
text