OID reference

skrClientCertificateTransfer

1.3.6.1.4.1.2.3.51.3.3.4.2.4.9.4.2

Description

For tftp mode, skrConfigFtpServer and skrConfigFileName must contain valid values. For sftp mode, skrConfigFTPCallUserID and skrConfigFtpCallPassword must also contain valid values. importSignedCertificate - Use this to import a signed certificate. To obtain a signed certificate, a certificate signing request (CSR) mu…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2.3.51.3.3.4.2.4.9.4 (skrClientConfigCertficate)
Node code
2
Node name
skrClientCertificateTransfer
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2.3.51.3.3.4.2.4.9.4.2
URN notation
urn:oid:1.3.6.1.4.1.2.3.51.3.3.4.2.4.9.4.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

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

Enumerated values

ValueName
1importSignedCertificate
2downloadCertificate
3downloadCSR

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

skrClientCertificateTransfer · mandatory

skrClientCertificateTransfer OBJECT-TYPE
                      SYNTAX  INTEGER {
                      importSignedCertificate(1),
                      downloadCertificate(2),
                      downloadCSR(3)
                      }
                      ACCESS  read-write
                      STATUS  mandatory
                      DESCRIPTION
                      "For tftp mode, skrConfigFtpServer and skrConfigFileName must contain valid values.
                      For sftp mode, skrConfigFTPCallUserID and skrConfigFtpCallPassword must also contain valid values.  
                      importSignedCertificate - 
                          Use this to import a signed certificate. To obtain a signed 
                          certificate, a certificate signing request (CSR) must first 
                          be generated and sent to a certificate authority (CA). The 
                          imported certificate must contain a public key that corresponds 
                          to the key pair previously generated by the generateNewKeyandCSR.
                      downloadCertificate - 
                          Use this link to download a copy of the currently installed 
                          certificate. The certificate will be in DER format. The contents 
                          of the certificate can be viewed using a third-party tool such as 
                          OpenSSL (www.openssl.org).  An example of the command line for 
                          viewing the contents of the certificate using OpenSSL would look 
                          something like the following:  
                          openssl x509 -in cert.der -inform DER -text  
                      downloadCSR - 
                          The file produced when creating a CSR is in DER or PEM format 
                          according to sslCertificateCSRDownloadFormat. If your CA expects 
                          the data in some other format, the file can be converted using a 
                          third-party tool such as OpenSSL(www.openssl.org). 
                          If the CA asks you to copy the contents of the CSR file into 
                          a web browser window, PEM format is usually expected.

                      NOTE: Value returned for the GET command is meaningless
                      for this MIB object."
                      ::= { skrClientConfigCertficate 2 }

skrClientCertificateTransfer · mandatory

skrClientCertificateTransfer OBJECT-TYPE
                      SYNTAX  INTEGER {
                      importSignedCertificate(1),
                      downloadCertificate(2),
                      downloadCSR(3)
                      }
                      ACCESS  read-write
                      STATUS  mandatory
                      DESCRIPTION
                      "For tftp mode, skrConfigFtpServer and skrConfigFileName must contain valid values.
                      For sftp mode, skrConfigFTPCallUserID and skrConfigFtpCallPassword must also contain valid values.  
                      importSignedCertificate - 
                          Use this to import a signed certificate. To obtain a signed 
                          certificate, a certificate signing request (CSR) must first 
                          be generated and sent to a certificate authority (CA). The 
                          imported certificate must contain a public key that corresponds 
                          to the key pair previously generated by the generateNewKeyandCSR.
                      downloadCertificate - 
                          Use this link to download a copy of the currently installed 
                          certificate. The certificate will be in DER format. The contents 
                          of the certificate can be viewed using a third-party tool such as 
                          OpenSSL (www.openssl.org).  An example of the command line for 
                          viewing the contents of the certificate using OpenSSL would look 
                          something like the following:  
                          openssl x509 -in cert.der -inform DER -text  
                      downloadCSR - 
                          The file produced when creating a CSR is in DER format. If your 
                          CA expects the data in some other format, such as PEM, the file 
                          can be converted using a third-party tool such as OpenSSL(www.openssl.org). 
                          If the CA asks you to copy the contents of the CSR file into 
                          a web browser window, PEM format is usually expected. An example 
                          of the command line for converting a CSR from DER to PEM format 
                          using OpenSSL would look something like the following:
                          openssl req -in csr.der -inform DER -out csr.pem -outform PEM 

                      NOTE: Value returned for the GET command is meaningless
                      for this MIB object."
                      ::= { skrClientConfigCertficate 2 }

Meaning

Descriptions

2 unique

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

Description 1

For tftp mode, skrConfigFtpServer and skrConfigFileName must contain valid values. For sftp mode, skrConfigFTPCallUserID and skrConfigFtpCallPassword must also contain valid values. importSignedCertificate - Use this to import a signed certificate. To obtain a signed certificate, a certificate signing request (CSR) must first be generated and sent to a certificate authority (CA). The imported certificate must contain a public key that corresponds to the key pair previously generated by the generateNewKeyandCSR. downloadCertificate - Use this link to download a copy of the currently installed certificate. The certificate will be in DER format. The contents of the certificate can be viewed using a third-party tool such as OpenSSL (www.openssl.org). An example of the command line for viewing the contents of the certificate using OpenSSL would look something like the following: openssl x509 -in cert.der -inform DER -text downloadCSR - The file produced when creating a CSR is in DER or PEM format according to sslCertificateCSRDownloadFormat. If your CA expects the data in some other format, the file can be converted using a third-party tool such as OpenSSL(www.openssl.org). If the CA asks you to copy the contents of the CSR file into a web browser window, PEM format is usually expected. NOTE: Value returned for the GET command is meaningless for this MIB object.

Sources for this description

IBM MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Description 2

For tftp mode, skrConfigFtpServer and skrConfigFileName must contain valid values. For sftp mode, skrConfigFTPCallUserID and skrConfigFtpCallPassword must also contain valid values. importSignedCertificate - Use this to import a signed certificate. To obtain a signed certificate, a certificate signing request (CSR) must first be generated and sent to a certificate authority (CA). The imported certificate must contain a public key that corresponds to the key pair previously generated by the generateNewKeyandCSR. downloadCertificate - Use this link to download a copy of the currently installed certificate. The certificate will be in DER format. The contents of the certificate can be viewed using a third-party tool such as OpenSSL (www.openssl.org). An example of the command line for viewing the contents of the certificate using OpenSSL would look something like the following: openssl x509 -in cert.der -inform DER -text downloadCSR - The file produced when creating a CSR is in DER format. If your CA expects the data in some other format, such as PEM, the file can be converted using a third-party tool such as OpenSSL(www.openssl.org). If the CA asks you to copy the contents of the CSR file into a web browser window, PEM format is usually expected. An example of the command line for converting a CSR from DER to PEM format using OpenSSL would look something like the following: openssl req -in csr.der -inform DER -out csr.pem -outform PEM NOTE: Value returned for the GET command is meaningless for this MIB object.

Sources for this description

IBM MIB copies (MibBrowser.online)

See 1 matching source record

Evidence

Source records

2 records

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

Records for description 1IBM MIB copies (LibreNMS/Observium Community)1 record · 2 sources

Description 1

skrClientCertificateTransfer · mandatoryIBM MIB copies (LibreNMS/Observium Community)2 sources

Status in source: mandatory.

Names: skrClientCertificateTransfer

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "skrClientCertificateTransfer",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "importSignedCertificate",
    "(",
    "1",
    ")",
    ",",
    "downloadCertificate",
    "(",
    "2",
    ")",
    ",",
    "downloadCSR",
    "(",
    "3",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"For tftp mode, skrConfigFtpServer and skrConfigFileName must contain valid values. For sftp mode, skrConfigFTPCallUserID and skrConfigFtpCallPassword must also contain valid values. importSignedCertificate - Use this to import a signed certificate. To obtain a signed certificate, a certificate signing request (CSR) must first be generated and sent to a certificate authority (CA). The imported certificate must contain a public key that corresponds to the key pair previously generated by the generateNewKeyandCSR. downloadCertificate - Use this link to download a copy of the currently installed certificate. The certificate will be in DER format. The contents of the certificate can be viewed using a third-party tool such as OpenSSL (www.openssl.org). An example of the command line for viewing the contents of the certificate using OpenSSL would look something like the following: openssl x509 -in cert.der -inform DER -text downloadCSR - The file produced when creating a CSR is in DER or PEM format according to sslCertificateCSRDownloadFormat. If your CA expects the data in some other format, the file can be converted using a third-party tool such as OpenSSL(www.openssl.org). If the CA asks you to copy the contents of the CSR file into a web browser window, PEM format is usually expected. NOTE: Value returned for the GET command is meaningless for this MIB object.\"",
    "::=",
    "{",
    "skrClientConfigCertficate",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "importSignedCertificate",
            1
          ],
          [
            "downloadCertificate",
            2
          ],
          [
            "downloadCSR",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "For tftp mode, skrConfigFtpServer and skrConfigFileName must contain valid values. For sftp mode, skrConfigFTPCallUserID and skrConfigFtpCallPassword must also contain valid values. importSignedCertificate - Use this to import a signed certificate. To obtain a signed certificate, a certificate signing request (CSR) must first be generated and sent to a certificate authority (CA). The imported certificate must contain a public key that corresponds to the key pair previously generated by the generateNewKeyandCSR. downloadCertificate - Use this link to download a copy of the currently installed certificate. The certificate will be in DER format. The contents of the certificate can be viewed using a third-party tool such as OpenSSL (www.openssl.org). An example of the command line for viewing the contents of the certificate using OpenSSL would look something like the following: openssl x509 -in cert.der -inform DER -text downloadCSR - The file produced when creating a CSR is in DER or PEM format according to sslCertificateCSRDownloadFormat. If your CA expects the data in some other format, the file can be converted using a third-party tool such as OpenSSL(www.openssl.org). If the CA asks you to copy the contents of the CSR file into a web browser window, PEM format is usually expected. NOTE: Value returned for the GET command is meaningless for this MIB object."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2IBM MIB copies (MibBrowser.online)1 record · 1 source

Description 2

skrClientCertificateTransfer · mandatoryIBM MIB copies (MibBrowser.online)1 source

Status in source: mandatory.

Names: skrClientCertificateTransfer

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "skrClientCertificateTransfer",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "importSignedCertificate",
    "(",
    "1",
    ")",
    ",",
    "downloadCertificate",
    "(",
    "2",
    ")",
    ",",
    "downloadCSR",
    "(",
    "3",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"For tftp mode, skrConfigFtpServer and skrConfigFileName must contain valid values. For sftp mode, skrConfigFTPCallUserID and skrConfigFtpCallPassword must also contain valid values. importSignedCertificate - Use this to import a signed certificate. To obtain a signed certificate, a certificate signing request (CSR) must first be generated and sent to a certificate authority (CA). The imported certificate must contain a public key that corresponds to the key pair previously generated by the generateNewKeyandCSR. downloadCertificate - Use this link to download a copy of the currently installed certificate. The certificate will be in DER format. The contents of the certificate can be viewed using a third-party tool such as OpenSSL (www.openssl.org). An example of the command line for viewing the contents of the certificate using OpenSSL would look something like the following: openssl x509 -in cert.der -inform DER -text downloadCSR - The file produced when creating a CSR is in DER format. If your CA expects the data in some other format, such as PEM, the file can be converted using a third-party tool such as OpenSSL(www.openssl.org). If the CA asks you to copy the contents of the CSR file into a web browser window, PEM format is usually expected. An example of the command line for converting a CSR from DER to PEM format using OpenSSL would look something like the following: openssl req -in csr.der -inform DER -out csr.pem -outform PEM NOTE: Value returned for the GET command is meaningless for this MIB object.\"",
    "::=",
    "{",
    "skrClientConfigCertficate",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "importSignedCertificate",
            1
          ],
          [
            "downloadCertificate",
            2
          ],
          [
            "downloadCSR",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "For tftp mode, skrConfigFtpServer and skrConfigFileName must contain valid values. For sftp mode, skrConfigFTPCallUserID and skrConfigFtpCallPassword must also contain valid values. importSignedCertificate - Use this to import a signed certificate. To obtain a signed certificate, a certificate signing request (CSR) must first be generated and sent to a certificate authority (CA). The imported certificate must contain a public key that corresponds to the key pair previously generated by the generateNewKeyandCSR. downloadCertificate - Use this link to download a copy of the currently installed certificate. The certificate will be in DER format. The contents of the certificate can be viewed using a third-party tool such as OpenSSL (www.openssl.org). An example of the command line for viewing the contents of the certificate using OpenSSL would look something like the following: openssl x509 -in cert.der -inform DER -text downloadCSR - The file produced when creating a CSR is in DER format. If your CA expects the data in some other format, such as PEM, the file can be converted using a third-party tool such as OpenSSL(www.openssl.org). If the CA asks you to copy the contents of the CSR file into a web browser window, PEM format is usually expected. An example of the command line for converting a CSR from DER to PEM format using OpenSSL would look something like the following: openssl req -in csr.der -inform DER -out csr.pem -outform PEM NOTE: Value returned for the GET command is meaningless for this MIB object."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2)

Bob Moore

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2.3.51.3.3.4.2.4.9.4.1 skrClientCertificateGeneration00
1.3.6.1.4.1.2.3.51.3.3.4.2.4.9.4.3 skrClientCertificateStatus00
1.3.6.1.4.1.2.3.51.3.3.4.2.4.9.4.4 skrClientCertificateExpirationDate00
1.3.6.1.4.1.2.3.51.3.3.4.2.4.9.4.5 skrClientCertificateRemove00