OID reference

ldapDomainSource

1.3.6.1.4.1.2.3.51.3.3.4.2.6.21

Description

The DNS SRV request sent to the DNS server must specify a domain name. The LDAP client will determine where to get this domain name based on one of the following three options: - extractSearchDomainFromLoginID: With this option, the LDAP client will use the domain name in the login id. For example, if the login id is …

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
21
Node name
ldapDomainSource
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2.3.51.3.3.4.2.6.21
URN notation
urn:oid:1.3.6.1.4.1.2.3.51.3.3.4.2.6.21
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 21}

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

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory

Enumerated values

ValueName
0extractSearchDomainFromLoginID
1useOnlyConfiguredSearchDomainBelow
2tryLoginFirstThenConfiguredValue

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.21.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

ldapDomainSource · mandatory

ldapDomainSource     OBJECT-TYPE  --IMM2-only
                      SYNTAX  INTEGER {
                        extractSearchDomainFromLoginID (0),
                        useOnlyConfiguredSearchDomainBelow (1),
                        tryLoginFirstThenConfiguredValue (2)
                      }
                      ACCESS  read-write
                      STATUS  mandatory
                      DESCRIPTION
                      "The DNS SRV request sent to the DNS server must specify a domain name. 
                      The LDAP client will determine where to get this domain name based on one 
                      of the following three options: 
                      
                        - extractSearchDomainFromLoginID: With this option, the LDAP client will 
                      use the domain name in the login id. For example, if the login id is 
                      joesmith@mycompany.com, the domain name equals mycompany.com. If the domain 
                      name cannot be extracted, the DNS SRV will fail, causing the user 
                      authentication to fail automatically.
                      
                        - useOnlyConfiguredSearchDomainBelow: With this option, the LDAP client 
                      will use the domain name configured in the Search Domain parameter. 
                      
                        - tryLoginFirstThenConfiguredValue: With this option, the LDAP client will 
                      first attempt to extract the domain name from the login id. If this succeeds, 
                      this domain name will be used in the DNS SRV request. If there is no domain 
                      name present in the login id, the LDAP client will instead use the configured 
                      Search Domain parameter as the domain name in the DNS SRV request. 
                      If nothing is configured, user authentication will fail immediately."
                      ::= { ldapClientCfg 21 }

ldapDomainSource · mandatory

ldapDomainSource     OBJECT-TYPE  --IMM2-only
                      SYNTAX  INTEGER {
                        extractSearchDomainFromLoginID (0),
                        useOnlyConfiguredSearchDomainBelow (1),
                        tryLoginFirstThenConfiguredValue (2)
                      }
                      ACCESS  read-write
                      STATUS  mandatory
                      DESCRIPTION
                      "The DNS SRV request sent to the DNS server must specify a domain name. 
                      The LDAP client will determine where to get this domain name based on one 
                      of the following three options: 
                      
                        - extractSearchDomainFromLoginID: With this option, the LDAP client will 
                      use the domain name in the login id. For example, if the login id is 
                      joesmith@mycompany.com, the domain name equals mycompany.com. If the domain 
                      name cannot be extracted, the DNS SRV will fail, causing the user 
                      authentication to fail automatically.
                      
                        - useOnlyConfiguredSearchDomainBelow: With this option, the LDAP client 
                      will use the domain name configured in the Search Domain parameter. 
                      
                        - tryLoginFirstThenConfiguredValue: With this option, the LDAP client will 
                      first attempt to extract the domain name from the login id. If this succeeds, 
                      this domain name will be used in the DNS SRV request. If there is no domain 
                      name present in the login id, the LDAP client will instead use the configured 
                      Search Domain parameter as the domain name in the DNS SRV request. 
                      If nothing is configured, user authentication will fail immediately."
                      ::= { ldapClientCfg 21 }

Meaning

Descriptions

1 unique

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

The DNS SRV request sent to the DNS server must specify a domain name. The LDAP client will determine where to get this domain name based on one of the following three options: - extractSearchDomainFromLoginID: With this option, the LDAP client will use the domain name in the login id. For example, if the login id is joesmith@mycompany.com, the domain name equals mycompany.com. If the domain name cannot be extracted, the DNS SRV will fail, causing the user authentication to fail automatically. - useOnlyConfiguredSearchDomainBelow: With this option, the LDAP client will use the domain name configured in the Search Domain parameter. - tryLoginFirstThenConfiguredValue: With this option, the LDAP client will first attempt to extract the domain name from the login id. If this succeeds, this domain name will be used in the DNS SRV request. If there is no domain name present in the login id, the LDAP client will instead use the configured Search Domain parameter as the domain name in the DNS SRV request. If nothing is configured, user authentication will fail immediately.

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

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

Status in source: mandatory.

Names: ldapDomainSource

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ldapDomainSource",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "extractSearchDomainFromLoginID",
    "(",
    "0",
    ")",
    ",",
    "useOnlyConfiguredSearchDomainBelow",
    "(",
    "1",
    ")",
    ",",
    "tryLoginFirstThenConfiguredValue",
    "(",
    "2",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The DNS SRV request sent to the DNS server must specify a domain name. The LDAP client will determine where to get this domain name based on one of the following three options: - extractSearchDomainFromLoginID: With this option, the LDAP client will use the domain name in the login id. For example, if the login id is joesmith@mycompany.com, the domain name equals mycompany.com. If the domain name cannot be extracted, the DNS SRV will fail, causing the user authentication to fail automatically. - useOnlyConfiguredSearchDomainBelow: With this option, the LDAP client will use the domain name configured in the Search Domain parameter. - tryLoginFirstThenConfiguredValue: With this option, the LDAP client will first attempt to extract the domain name from the login id. If this succeeds, this domain name will be used in the DNS SRV request. If there is no domain name present in the login id, the LDAP client will instead use the configured Search Domain parameter as the domain name in the DNS SRV request. If nothing is configured, user authentication will fail immediately.\"",
    "::=",
    "{",
    "ldapClientCfg",
    "21",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "extractSearchDomainFromLoginID",
            0
          ],
          [
            "useOnlyConfiguredSearchDomainBelow",
            1
          ],
          [
            "tryLoginFirstThenConfiguredValue",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The DNS SRV request sent to the DNS server must specify a domain name. The LDAP client will determine where to get this domain name based on one of the following three options: - extractSearchDomainFromLoginID: With this option, the LDAP client will use the domain name in the login id. For example, if the login id is joesmith@mycompany.com, the domain name equals mycompany.com. If the domain name cannot be extracted, the DNS SRV will fail, causing the user authentication to fail automatically. - useOnlyConfiguredSearchDomainBelow: With this option, the LDAP client will use the domain name configured in the Search Domain parameter. - tryLoginFirstThenConfiguredValue: With this option, the LDAP client will first attempt to extract the domain name from the login id. If this succeeds, this domain name will be used in the DNS SRV request. If there is no domain name present in the login id, the LDAP client will instead use the configured Search Domain parameter as the domain name in the DNS SRV request. If nothing is configured, user authentication will fail immediately."
    ],
    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.10 ldapUserSearchBaseDN00
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.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