OID reference

bosUsmUserAuthKeyChange

1.3.6.1.4.1.1411.102.102.11.1.1.1.6

Description

An object, which when modified, causes the secret authentication key used for messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, to be modified via a one-way function. The associated protocol is the usmUserAuthProtocol. The associated secret key is the user's secret authenticat…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1411.102.102.11.1.1.1 (bosUsmUserEntry)
Node code
6
Node name
bosUsmUserAuthKeyChange
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1411.102.102.11.1.1.1.6
URN notation
urn:oid:1.3.6.1.4.1.1411.102.102.11.1.1.1.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1411 102 102 11 1 1 1 6}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserAuthKeyChange(6)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1411/102/102/11/1/1/1/6
  • /ISO/Identified-Organization/6/1/4/1/1411/102/102/11/1/1/1/6
  • /ISO/3/6/1/4/1/1411/102/102/11/1/1/1/6
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/identified-organization/dod/internet/private/enterprise/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/identified-organization/dod/internet/private/enterprises/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/identified-organization/dod/internet/private/enterprises/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/identified-organization/dod/internet/private/vendor-objects/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/identified-organization/dod/internet/private/vendor-objects/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/org/dod/internet/private/enterprise/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/org/dod/internet/private/enterprise/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/org/dod/internet/private/enterprises/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/org/dod/internet/private/enterprises/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/org/dod/internet/private/ldap-enterprise/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/org/dod/internet/private/ldap-enterprise/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/org/dod/internet/private/vendor-objects/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • /iso/org/dod/internet/private/vendor-objects/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserAuthKeyChange
  • Additional combinations skipped.

SNMP properties

Value type
BosKeyChange
Maximum access defined by MIB
read-create
Status in MIB
current
Default value
''H

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

bosUsmUserAuthKeyChange OBJECT-TYPE
    SYNTAX       BosKeyChange   -- typically (SIZE (0 | 32)) for HMACMD5
                             -- typically (SIZE (0 | 40)) for HMACSHA
    MAX-ACCESS   read-create
    STATUS       current
    DESCRIPTION "An object, which when modified, causes the secret
                 authentication key used for messages sent on behalf
                 of this user to/from the SNMP engine identified by
                 usmUserEngineID, to be modified via a one-way
                 function.

                 The associated protocol is the usmUserAuthProtocol.
                 The associated secret key is the user's secret
                 authentication key (authKey). The associated hash
                 algorithm is the algorithm used by the user's
                 usmUserAuthProtocol.

                 When creating a new user, it is an 'inconsistentName'
                 error for a set operation to refer to this object
                 unless it is previously or concurrently initialized
                 through a set operation on the corresponding instance
                 of usmUserCloneFrom.

                 When the value of the corresponding usmUserAuthProtocol
                 is usmNoAuthProtocol, then a set is successful, but
                 effectively is a no-op.

                 When this object is read, the zero-length (empty)
                 string is returned.

                 The recommended way to do a key change is as follows:

                   1) GET(usmUserSpinLock.0) and save in sValue.
                   2) generate the keyChange value based on the old
                      (existing) secret key and the new secret key,
                      let us call this kcValue.

                 If you do the key change on behalf of another user:

                   3) SET(usmUserSpinLock.0=sValue,
                          usmUserAuthKeyChange=kcValue
                          usmUserPublic=randomValue)

                 If you do the key change for yourself:

                   4) SET(usmUserSpinLock.0=sValue,
                          usmUserOwnAuthKeyChange=kcValue
                          usmUserPublic=randomValue)

                 If you get a response with error-status of noError,
                 then the SET succeeded and the new key is active.
                 If you do not get a response, then you can issue a
                 GET(usmUserPublic) and check if the value is equal
                 to the randomValue you did send in the SET. If so, then
                 the key change succeeded and the new key is active
                 (probably the response got lost). If not, then the SET
                 request probably never reached the target and so you
                 can start over with the procedure above.
                "
    DEFVAL      { ''H }    -- the empty string
    ::= { bosUsmUserEntry 6 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

An object, which when modified, causes the secret authentication key used for messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, to be modified via a one-way function. The associated protocol is the usmUserAuthProtocol. The associated secret key is the user's secret authentication key (authKey). The associated hash algorithm is the algorithm used by the user's usmUserAuthProtocol. When creating a new user, it is an 'inconsistentName' error for a set operation to refer to this object unless it is previously or concurrently initialized through a set operation on the corresponding instance of usmUserCloneFrom. When the value of the corresponding usmUserAuthProtocol is usmNoAuthProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. The recommended way to do a key change is as follows: 1) GET(usmUserSpinLock.0) and save in sValue. 2) generate the keyChange value based on the old (existing) secret key and the new secret key, let us call this kcValue. If you do the key change on behalf of another user: 3) SET(usmUserSpinLock.0=sValue, usmUserAuthKeyChange=kcValue usmUserPublic=randomValue) If you do the key change for yourself: 4) SET(usmUserSpinLock.0=sValue, usmUserOwnAuthKeyChange=kcValue usmUserPublic=randomValue) If you get a response with error-status of noError, then the SET succeeded and the new key is active. If you do not get a response, then you can issue a GET(usmUserPublic) and check if the value is equal to the randomValue you did send in the SET. If so, then the key change succeeded and the new key is active (probably the response got lost). If not, then the SET request probably never reached the target and so you can start over with the procedure above.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

bosUsmUserAuthKeyChange · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: bosUsmUserAuthKeyChange

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bosUsmUserAuthKeyChange",
    "OBJECT-TYPE",
    "SYNTAX",
    "BosKeyChange",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"An object, which when modified, causes the secret authentication key used for messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, to be modified via a one-way function. The associated protocol is the usmUserAuthProtocol. The associated secret key is the user's secret authentication key (authKey). The associated hash algorithm is the algorithm used by the user's usmUserAuthProtocol. When creating a new user, it is an 'inconsistentName' error for a set operation to refer to this object unless it is previously or concurrently initialized through a set operation on the corresponding instance of usmUserCloneFrom. When the value of the corresponding usmUserAuthProtocol is usmNoAuthProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. The recommended way to do a key change is as follows: 1) GET(usmUserSpinLock.0) and save in sValue. 2) generate the keyChange value based on the old (existing) secret key and the new secret key, let us call this kcValue. If you do the key change on behalf of another user: 3) SET(usmUserSpinLock.0=sValue, usmUserAuthKeyChange=kcValue usmUserPublic=randomValue) If you do the key change for yourself: 4) SET(usmUserSpinLock.0=sValue, usmUserOwnAuthKeyChange=kcValue usmUserPublic=randomValue) If you get a response with error-status of noError, then the SET succeeded and the new key is active. If you do not get a response, then you can issue a GET(usmUserPublic) and check if the value is equal to the randomValue you did send in the SET. If so, then the key change succeeded and the new key is active (probably the response got lost). If not, then the SET request probably never reached the target and so you can start over with the procedure above. \"",
    "DEFVAL",
    "{",
    "'",
    "'",
    "H",
    "}",
    "::=",
    "{",
    "bosUsmUserEntry",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "BosKeyChange"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "An object, which when modified, causes the secret authentication key used for messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, to be modified via a one-way function. The associated protocol is the usmUserAuthProtocol. The associated secret key is the user's secret authentication key (authKey). The associated hash algorithm is the algorithm used by the user's usmUserAuthProtocol. When creating a new user, it is an 'inconsistentName' error for a set operation to refer to this object unless it is previously or concurrently initialized through a set operation on the corresponding instance of usmUserCloneFrom. When the value of the corresponding usmUserAuthProtocol is usmNoAuthProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. The recommended way to do a key change is as follows: 1) GET(usmUserSpinLock.0) and save in sValue. 2) generate the keyChange value based on the old (existing) secret key and the new secret key, let us call this kcValue. If you do the key change on behalf of another user: 3) SET(usmUserSpinLock.0=sValue, usmUserAuthKeyChange=kcValue usmUserPublic=randomValue) If you do the key change for yourself: 4) SET(usmUserSpinLock.0=sValue, usmUserOwnAuthKeyChange=kcValue usmUserPublic=randomValue) If you get a response with error-status of noError, then the SET succeeded and the new key is active. If you do not get a response, then you can issue a GET(usmUserPublic) and check if the value is equal to the randomValue you did send in the SET. If so, then the key change succeeded and the new key is active (probably the response got lost). If not, then the SET request probably never reached the target and so you can start over with the procedure above."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "''H"
    ]
  ]
}
  • Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive.

    Module: EX2500-BASE-MIB

    See published definition above

    Module imports
    {'IF-MIB': ['ifIndex', 'InterfaceIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'DisplayString', 'PhysAddress', 'MacAddress', 'RowStatus', 'TimeInterval', 'TimeStamp'], 'BRIDGE-MIB': ['BridgeId', 'dot1dTp', 'dot1dTpPort', 'dot1dBridge', 'dot1dBasePortEntry', 'dot1dBasePort'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-IDENTITY', 'enterprises', 'Integer32', 'Unsigned32', 'Counter32', 'Gauge32', 'Counter64', 'TimeTicks', 'IpAddress', 'mib-2'], 'RFC1213-MIB': ['sysName', 'sysLocation', 'sysContact', 'ifIndex'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'P-BRIDGE-MIB': ['EnabledStatus'], 'Q-BRIDGE-MIB': ['PortList'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString', 'SnmpEngineID', 'SnmpMessageProcessingModel', 'SnmpSecurityModel', 'SnmpSecurityLevel'], 'SNMP-USER-BASED-SM-MIB': ['usmNoAuthProtocol', 'usmNoPrivProtocol']}
    · Download EX2500-BASE-MIB

    Related source files and packages:

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1411)

Walsh Kevin

Siblings (12)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1411.102.102.11.1.1.1.1 bosUsmUserTableIndex00
1.3.6.1.4.1.1411.102.102.11.1.1.1.2 bosUsmUserName00
1.3.6.1.4.1.1411.102.102.11.1.1.1.3 bosUsmUserSecurityName00
1.3.6.1.4.1.1411.102.102.11.1.1.1.4 bosUsmUserCloneFrom00
1.3.6.1.4.1.1411.102.102.11.1.1.1.5 bosUsmUserAuthProtocol00
1.3.6.1.4.1.1411.102.102.11.1.1.1.7 bosUsmUserOwnAuthKeyChange00
1.3.6.1.4.1.1411.102.102.11.1.1.1.8 bosUsmUserPrivProtocol00
1.3.6.1.4.1.1411.102.102.11.1.1.1.9 bosUsmUserPrivKeyChange00
1.3.6.1.4.1.1411.102.102.11.1.1.1.10 bosUsmUserOwnPrivKeyChange00
1.3.6.1.4.1.1411.102.102.11.1.1.1.11 bosUsmUserPublic00
1.3.6.1.4.1.1411.102.102.11.1.1.1.12 bosUsmUserStorageType00
1.3.6.1.4.1.1411.102.102.11.1.1.1.13 bosUsmUserStatus00