OID reference

ldapUserSearchBaseDN

1.3.6.1.4.1.2.3.51.3.3.4.2.6.10

Description

As part of the user authentication process, it is necessary to search the LDAP server for one or more attributes associated with a particular user. Any search request must specify the base DN for the actual search. This field specifies the base DN which should be used to search the User directory. An example might loo…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2.3.51.3.3.4.2.6 (ldapClientCfg)
Node code
10
Node name
ldapUserSearchBaseDN
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2.3.51.3.3.4.2.6.10
URN notation
urn:oid:1.3.6.1.4.1.2.3.51.3.3.4.2.6.10
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2 3 51 3 3 4 2 6 10}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) ibmIntegratedManagementModuleMIB(3) configureSP(3) networkConfiguration(4) tcpProtocols(2) ldapClientCfg(6) ldapUserSearchBaseDN(10)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2/3/51/3/3/4/2/6/10
  • /ISO/Identified-Organization/6/1/4/1/2/3/51/3/3/4/2/6/10
  • /ISO/3/6/1/4/1/2/3/51/3/3/4/2/6/10
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/ibm/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/identified-organization/dod/internet/private/enterprise/IBM/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/identified-organization/dod/internet/private/enterprise/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/identified-organization/dod/internet/private/enterprises/ibm/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/identified-organization/dod/internet/private/enterprises/IBM/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/identified-organization/dod/internet/private/enterprises/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/ibm/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/IBM/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/identified-organization/dod/internet/private/vendor-objects/ibm/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/identified-organization/dod/internet/private/vendor-objects/IBM/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/identified-organization/dod/internet/private/vendor-objects/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/org/dod/internet/private/enterprise/ibm/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/org/dod/internet/private/enterprise/IBM/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/org/dod/internet/private/enterprise/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • /iso/org/dod/internet/private/enterprises/ibm/ibmAgents/netfinitySupportProcessorAgent/ibmIntegratedManagementModuleMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
  • Additional combinations skipped.

SNMP properties

Value type
OCTET STRING
Maximum access defined by MIB
read-write
Status in MIB
deprecated
Allowed size (octets)
0–64

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.2.3.51.3.3.4.2.6.10.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

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

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

ldapUserSearchBaseDN · deprecated

ldapUserSearchBaseDN     OBJECT-TYPE
                      SYNTAX  OCTET STRING (SIZE(0..64))
                      ACCESS  read-write
                      STATUS  deprecated
                      DESCRIPTION
                      "As part of the user authentication process, it is necessary to search 
                      the LDAP server for one or more attributes associated with a particular 
                      user. Any search request must specify the base DN for the actual search. 
                      This field specifies the base DN which should be used to search the User 
                      directory. An example might look like cn=users,dn=foobar,dn=com. If this 
                      field is left blank, the Root DN will be used as the search base instead.
                      As mentioned, user searches are part of the authentication process. They 
                      are carried out to retrieve information about the user such as login 
                      permissions, callback number, and group memberships. For Version 2.0 LDAP 
                      clients, it is strongly encouraged that this parameter be configured, 
                      otherwise a search using the root DN may not succeed (as seen on Active 
                      Directory servers).

                      NOTE: This Mib object is deprecated and no longer supported."
                      ::= { ldapClientCfg 10 }

ldapUserSearchBaseDN · deprecated

ldapUserSearchBaseDN     OBJECT-TYPE
                      SYNTAX  OCTET STRING (SIZE(0..64))
                      ACCESS  read-write
                      STATUS  deprecated
                      DESCRIPTION
                      "As part of the user authentication process, it is necessary to search 
                      the LDAP server for one or more attributes associated with a particular 
                      user. Any search request must specify the base DN for the actual search. 
                      This field specifies the base DN which should be used to search the User 
                      directory. An example might look like cn=users,dn=foobar,dn=com. If this 
                      field is left blank, the Root DN will be used as the search base instead.
                      As mentioned, user searches are part of the authentication process. They 
                      are carried out to retrieve information about the user such as login 
                      permissions, callback number, and group memberships. For Version 2.0 LDAP 
                      clients, it is strongly encouraged that this parameter be configured, 
                      otherwise a search using the root DN may not succeed (as seen on Active 
                      Directory servers).

                      NOTE: This Mib object is deprecated and no longer supported."
                      ::= { ldapClientCfg 10 }

Meaning

Descriptions

1 unique

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

As part of the user authentication process, it is necessary to search the LDAP server for one or more attributes associated with a particular user. Any search request must specify the base DN for the actual search. This field specifies the base DN which should be used to search the User directory. An example might look like cn=users,dn=foobar,dn=com. If this field is left blank, the Root DN will be used as the search base instead. As mentioned, user searches are part of the authentication process. They are carried out to retrieve information about the user such as login permissions, callback number, and group memberships. For Version 2.0 LDAP clients, it is strongly encouraged that this parameter be configured, otherwise a search using the root DN may not succeed (as seen on Active Directory servers). NOTE: This Mib object is deprecated and no longer supported.

Sources for this description

IBM MIB copies (LibreNMS/Observium Community)IBM MIB copies (MibBrowser.online)

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 1IBM MIB copies (LibreNMS/Observium Community), IBM MIB copies (MibBrowser.online)1 record · 3 sources

Description 1

ldapUserSearchBaseDN · deprecatedIBM MIB copies (LibreNMS/Observium Community), IBM MIB copies (MibBrowser.online)3 sources

Status in source: deprecated.

Names: ldapUserSearchBaseDN

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ldapUserSearchBaseDN",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "(",
    "SIZE",
    "(",
    "0",
    ".",
    ".",
    "64",
    ")",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"As part of the user authentication process, it is necessary to search the LDAP server for one or more attributes associated with a particular user. Any search request must specify the base DN for the actual search. This field specifies the base DN which should be used to search the User directory. An example might look like cn=users,dn=foobar,dn=com. If this field is left blank, the Root DN will be used as the search base instead. As mentioned, user searches are part of the authentication process. They are carried out to retrieve information about the user such as login permissions, callback number, and group memberships. For Version 2.0 LDAP clients, it is strongly encouraged that this parameter be configured, otherwise a search using the root DN may not succeed (as seen on Active Directory servers). NOTE: This Mib object is deprecated and no longer supported.\"",
    "::=",
    "{",
    "ldapClientCfg",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING",
      [
        "octetStringSubType",
        [
          [
            0,
            64
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "As part of the user authentication process, it is necessary to search the LDAP server for one or more attributes associated with a particular user. Any search request must specify the base DN for the actual search. This field specifies the base DN which should be used to search the User directory. An example might look like cn=users,dn=foobar,dn=com. If this field is left blank, the Root DN will be used as the search base instead. As mentioned, user searches are part of the authentication process. They are carried out to retrieve information about the user such as login permissions, callback number, and group memberships. For Version 2.0 LDAP clients, it is strongly encouraged that this parameter be configured, otherwise a search using the root DN may not succeed (as seen on Active Directory servers). NOTE: This Mib object is deprecated and no longer supported."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2)

Bob Moore

Siblings (24)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2.3.51.3.3.4.2.6.1 ldapServer1NameOrIPAddress00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.2 ldapServer1PortNumber00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.3 ldapServer2NameOrIPAddress00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.4 ldapServer2PortNumber00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.5 ldapServer3NameOrIPAddress00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.6 ldapServer3PortNumber00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.7 ldapServer4NameOrIPAddress00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.8 ldapServer4PortNumber00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.9 ldapRootDN00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.11 ldapGroupFilter00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.12 ldapBindingMethod00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.13 ldapClientAuthenticationDN00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.14 ldapClientAuthenticationPassword00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.15 ldapRoleBasedSecurityEnabled00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.16 ldapServerTargetName00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.17 ldapUIDsearchAttribute00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.18 ldapGroupSearchAttribute00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.19 ldapLoginPermissionAttribute00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.20 ldapUseDNSOrPreConfiguredServers00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.21 ldapDomainSource00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.22 ldapForestName00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.23 ldapAuthCfg00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.24 ldapSearchDomain00
1.3.6.1.4.1.2.3.51.3.3.4.2.6.25 ldapServiceName00