2.5. Object Identifier Name Mapping

Provides a map of pairs which specifies human readable names for Object Identifiers (OIDs). That map is stored as a standard Java properties file in the settings directory of the application by default. The configuration item “oid-map” allows to specify any file at any location for this purpose. This allows to share the same mapping information for multiple applications.

If no such file exists or the specified file cannot be found, only the embedded default mappings will be available, which is a fixed set of well known OIDs commonly in use in publicly standardized areas. When a mapping file is found, the mappings found therein will extend the embedded map rather than replacing it. So there is no need to replicate the embedded mappings in the provided customization file. It can be used to provide additional mappings which are not publicly known for example.

The contents of the file should contain the numbered representation of an OID as its key and its human readable name as its value, e.g.

  2 = joint-iso-itu-t
  2.1 = asn1
  2.1.1 = basic-encoding
Which will result in the display of OIDs as follows:
  2     => joint-iso-itu-t(2)
  2.1   => joint-iso-itu-t(2) asn1(1)
  2.1.1 => joint-iso-itu-t(2) asn1(1) basic-encoding(1)

This configuration allows to get some information on data of unknown origin without the need to access and/or interpret the corresponding ASN.1 syntax definition. For example many of the security related data types contain an OID which identifies the following object, e.g. the OID

    => iso(1) member-body(2) USA(840) RSADSI(113549)
         PKCS(1) pkcs-1(1) md5withRSAEncryption(4)
specifies a cryptographic signature which consists of an RSA-encrypted MD5-hash which is stored according to the PKCS-1 standard of the US firm RSADSI which is an ISO member.