All MIBs › SNMP-USER-BASED-SM-MIB › usmUserAuthProtocol
usmUserAuthProtocol
Module: SNMP-USER-BASED-SM-MIB
OID (symbolic): SNMP-USER-BASED-SM-MIB::usmUserAuthProtocol
OID (numeric): 1.3.6.1.6.3.15.1.2.2.1.5
Node type: OBJECT-TYPE
Type: AutonomousType
Access: read-create
Description:
An indication of whether messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, can be authenticated, and if so, the type of authentication protocol which is used.
An instance of this object is created concurrently with the creation of any other object instance for the same user (i.e., as part of the processing of the set operation which creates the first object instance in the same conceptual row).
If an initial set operation (i.e. at row creation time) tries to set a value for an unknown or unsupported protocol, then a 'wrongValue' error must be returned.
The value will be overwritten/set when a set operation is performed on the corresponding instance of usmUserCloneFrom.
Once instantiated, the value of such an instance of this object can only be changed via a set operation to the value of the usmNoAuthProtocol.
If a set operation tries to change the value of an
existing instance of this object to any value other than usmNoAuthProtocol, then an 'inconsistentValue' error must be returned.
If a set operation tries to set the value to the usmNoAuthProtocol while the usmUserPrivProtocol value in the same row is not equal to usmNoPrivProtocol, then an 'inconsistentValue' error must be returned. That means that an SNMP command generator application must first ensure that the usmUserPrivProtocol is set to the usmNoPrivProtocol value before it can set the usmUserAuthProtocol value to usmNoAuthProtocol.
What is usmUserAuthProtocol?
This object specifies which authentication protocol (such as HMAC-MD5 or HMAC-SHA) a particular SNMPv3 user account should use to verify the identity and integrity of SNMP messages. The protocol determines how messages are digitally signed to prevent tampering and ensure the sender is legitimate. An administrator would configure this during user setup to enforce specific security levels and organizational security policies.
OID Breakdown
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | BIANCA-BRICK-PPP-MIB |
| 1.3.6 | dod | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1 | internet | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.6 | snmpV2 | DASAN-DHCP-MIB |
| 1.3.6.1.6.3 | snmpModules | RAPID-CITY |
| 1.3.6.1.6.3.15 | snmpUsmMIB | SNMP-USER-BASED-SM-MIB |
| 1.3.6.1.6.3.15.1 | usmMIBObjects | SNMP-USER-BASED-SM-MIB |
| 1.3.6.1.6.3.15.1.2 | usmUser | SNMP-USER-BASED-SM-MIB |
| 1.3.6.1.6.3.15.1.2.2 | usmUserTable | SNMP-USER-BASED-SM-MIB |
| 1.3.6.1.6.3.15.1.2.2.1 | usmUserEntry | SNMP-USER-BASED-SM-MIB |
| 1.3.6.1.6.3.15.1.2.2.1.5 | usmUserAuthProtocol | SNMP-USER-BASED-SM-MIB |