Behaves exactly as usmUserPrivKeyChange, with one
notable difference: in order for the Set operation
to succeed, the usmUserName of the operation
requester must match the usmUserName that indexes
the row which is targeted by this operation.
In addition, the USM security model must be
used for this operation.
The idea here is that access to this column can be
public, since it will only allow a user to change
his own secret privacy key (privKey).
Note that this can only be done once the row is active.
When a set is received and the usmUserName of the
requester is not the same as the umsUserName that
indexes the row which is targeted by this operation,
then a 'noAccess' error must be returned.
When a set is received and the security model in use
is not USM, then a 'noAccess' error must be returned.
Parsed from file SNMP-USER-BASED-SM-MIB.mib
Module: SNMP-USER-BASED-SM-MIB
Behaves exactly as usmUserPrivKeyChange, with one
notable difference: in order for the Set operation
to succeed, the usmUserName of the operation
requester must match the usmUserName that indexes
the row which is targeted by this operation.
In addition, the USM security model must be
used for this operation.
The idea here is that access to this column can be
public, since it will only allow a user to change
his own secret privacy key (privKey).
Note that this can only be done once the row is active.
When a set is received and the usmUserName of the
requester is not the same as the umsUserName that
indexes the row which is targeted by this operation,
then a 'noAccess' error must be returned.
When a set is received and the security model in use
is not USM, then a 'noAccess' error must be returned.
usmUserOwnPrivKeyChange OBJECT-TYPE
SYNTAX KeyChange -- typically (SIZE (0 | 32)) for DES
MAX-ACCESS read-create
STATUS current
DESCRIPTION "Behaves exactly as usmUserPrivKeyChange, with one
notable difference: in order for the Set operation
to succeed, the usmUserName of the operation
requester must match the usmUserName that indexes
the row which is targeted by this operation.
In addition, the USM security model must be
used for this operation.
The idea here is that access to this column can be
public, since it will only allow a user to change
his own secret privacy key (privKey).
Note that this can only be done once the row is active.
When a set is received and the usmUserName of the
requester is not the same as the umsUserName that
indexes the row which is targeted by this operation,
then a
oAccess error must be returned.
When a set is received and the security model in use
is not USM, then a
oAccess error must be returned.
"
DEFVAL { H } -- the empty string
View at oid-info.com
Behaves exactly as usmUserPrivKeyChange, with one
notable difference: in order for the Set operation
to succeed, the usmUserName of the operation
requester must match the usmUserName that indexes
the row which is targeted by this operation.
In addition, the USM security model must be
used for this operation.
The idea here is that access to this column can be
public, since it will only allow a user to change
his own secret privacy key (privKey).
Note that this can only be done once the row is active.
When a set is received and the usmUserName of the
requester is not the same as the umsUserName that
indexes the row which is targeted by this operation,
then a 'noAccess' error must be returned.
When a set is received and the security model in use
is not USM, then a 'noAccess' error must be returned.
Parsed from file rfc3414.mib.txt
Company: None
Module: SNMP-USER-BASED-SM-MIB
Behaves exactly as usmUserPrivKeyChange, with one
notable difference: in order for the Set operation
to succeed, the usmUserName of the operation
requester must match the usmUserName that indexes
the row which is targeted by this operation.
In addition, the USM security model must be
used for this operation.
The idea here is that access to this column can be
public, since it will only allow a user to change
his own secret privacy key (privKey).
Note that this can only be done once the row is active.
When a set is received and the usmUserName of the
requester is not the same as the umsUserName that
indexes the row which is targeted by this operation,
then a 'noAccess' error must be returned.
When a set is received and the security model in use
is not USM, then a 'noAccess' error must be returned.
usmUserOwnPrivKeyChange OBJECT-TYPE SYNTAX KeyChange MAX-ACCESS read-create STATUS current DESCRIPTION "Behaves exactly as usmUserPrivKeyChange, with one notable difference: in order for the Set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation. In addition, the USM security model must be used for this operation. The idea here is that access to this column can be public, since it will only allow a user to change his own secret privacy key (privKey). Note that this can only be done once the row is active. When a set is received and the usmUserName of the requester is not the same as the umsUserName that indexes the row which is targeted by this operation, then a 'noAccess' error must be returned. When a set is received and the security model in use is not USM, then a 'noAccess' error must be returned. " DEFVAL { ''H } ::= { usmUserEntry 10 }
usmUserOwnPrivKeyChange OBJECT-TYPE SYNTAX KeyChange ACCESS read-write STATUS mandatory DESCRIPTION "Behaves exactly as usmUserPrivKeyChange, with one notable difference: in order for the Set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation. In addition, the USM security model must be used for this operation. The idea here is that access to this column can be public, since it will only allow a user to change his own secret privacy key (privKey). Note that this can only be done once the row is active. When a set is received and the usmUserName of the requester is not the same as the umsUserName that indexes the row which is targeted by this operation, then a 'noAccess' error must be returned. When a set is received and the security model in use is not USM, then a 'noAccess' error must be returned." DEFVAL { ''H } ::= { usmUserEntry 10 }
Automatically extracted from RFC3414
usmUserOwnPrivKeyChange OBJECT-TYPE SYNTAX KeyChange MAX-ACCESS read-create STATUS current DESCRIPTION "Behaves exactly as usmUserPrivKeyChange, with one notable difference: in order for the Set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation. In addition, the USM security model must be used for this operation. The idea here is that access to this column can be public, since it will only allow a user to change his own secret privacy key (privKey). Note that this can only be done once the row is active. When a set is received and the usmUserName of the requester is not the same as the umsUserName that indexes the row which is targeted by this operation, then a 'noAccess' error must be returned. When a set is received and the security model in use is not USM, then a 'noAccess' error must be returned. " DEFVAL { ''H } ::= { usmUserEntry 10 }
usmUserOwnPrivKeyChange OBJECT-TYPE SYNTAX KeyChange MAX-ACCESS read-create STATUS current DESCRIPTION "Behaves exactly as usmUserPrivKeyChange, with one notable difference: in order for the Set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation. In addition, the USM security model must be used for this operation. The idea here is that access to this column can be public, since it will only allow a user to change his own secret privacy key (privKey). Note that this can only be done once the row is active. When a set is received and the usmUserName of the requester is not the same as the umsUserName that indexes the row which is targeted by this operation, then a 'noAccess' error must be returned. When a set is received and the security model in use is not USM, then a 'noAccess' error must be returned. " DEFVAL { ''H } ::= { usmUserEntry 10 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.6.3.15.1.2.2.1.1 | usmUserEngineID | 0 | 0 | An SNMP engine's administratively-unique identifier. In a simple agent, this value is always that agent's own snmpEngineID value.… |
| 1.3.6.1.6.3.15.1.2.2.1.2 | usmUserName | 0 | 0 | A human readable string representing the name of the user. This is the (User-based Security) Model dependent security ID. |
| 1.3.6.1.6.3.15.1.2.2.1.3 | usmUserSecurityName | 0 | 0 | A human readable string representing the user in Security Model independent format. The default transformation of the User-based … |
| 1.3.6.1.6.3.15.1.2.2.1.4 | usmUserCloneFrom | 0 | 0 | A pointer to another conceptual row in this usmUserTable. The user in this other conceptual row is called the clone-from user. Wh… |
| 1.3.6.1.6.3.15.1.2.2.1.5 | usmUserAuthProtocol | 0 | 0 | An indication of whether messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, can be authe… |
| 1.3.6.1.6.3.15.1.2.2.1.6 | usmUserAuthKeyChange | 0 | 0 | An object, which when modified, causes the secret authentication key used for messages sent on behalf of this user to/from the SN… |
| 1.3.6.1.6.3.15.1.2.2.1.7 | usmUserOwnAuthKeyChange | 0 | 0 | Behaves exactly as usmUserAuthKeyChange, with one notable difference: in order for the set operation to succeed, the usmUserName … |
| 1.3.6.1.6.3.15.1.2.2.1.8 | usmUserPrivProtocol | 0 | 0 | An indication of whether messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, can be prote… |
| 1.3.6.1.6.3.15.1.2.2.1.9 | usmUserPrivKeyChange | 0 | 0 | An object, which when modified, causes the secret encryption key used for messages sent on behalf of this user to/from the SNMP e… |
| 1.3.6.1.6.3.15.1.2.2.1.11 | usmUserPublic | 0 | 0 | A publicly-readable value which can be written as part of the procedure for changing a user's secret authentication and/or privac… |
| 1.3.6.1.6.3.15.1.2.2.1.12 | usmUserStorageType | 0 | 0 | The storage type for this conceptual row. Conceptual rows having the value 'permanent' must allow write-access at a minimum to: - … |
| 1.3.6.1.6.3.15.1.2.2.1.13 | usmUserStatus | 0 | 0 | The status of this conceptual row. Until instances of all corresponding columns are appropriately configured, the value of the cor… |