| OID | 1.3.6.1.6.3.15.1.2.2.1.10 |
| Module | SNMP-USER-BASED-SM-MIB (CISCO) |
| Nom | usmUserOwnPrivKeyChange |
| Acces | readwrite |
| 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. |
| Syntaxe | KeyChange (SNMP-USER-BASED-SM-MIB) |
| Module | SNMP-USER-BASED-SM-MIB (DELL) |
| Nom | usmUserOwnPrivKeyChange |
| Acces | readwrite |
| 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. |
| Syntaxe | KeyChange (SNMP-USER-BASED-SM-MIB) |
| Module | SNMP-USER-BASED-SM-MIB (ietf) |
| Nom | usmUserOwnPrivKeyChange |
| Acces | readwrite |
| 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. |
| Syntaxe | KeyChange (SNMP-USER-BASED-SM-MIB) |
| Module | SNMP-USER-BASED-SM-MIB (Alcatel) |
| Nom | usmUserOwnPrivKeyChange |
| Acces | readwrite |
| 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. |
| Syntaxe | KeyChange (SNMP-USER-BASED-SM-MIB) |
| Module | SNMP-USER-BASED-SM-MIB (FS) |
| Nom | usmUserOwnPrivKeyChange |
| Acces | readwrite |
| 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. |
| Syntaxe | KeyChange (SNMP-USER-BASED-SM-MIB) |