The GET /MetadataFields/{name} method is used to return details for the metadata
Metadata provides information about a piece of data. It is used to summarize basic information about data, which can make working with the data easier. In Keyfactor Command, the certificate metadata feature allows you to create custom metadata fields that allow you to tag certificates with tracking information about certificates. field with the specified unique name. This method returns HTTP 200 OK on a success with details for the requested metadata field.
Table 536: GET Metadata Fields {name} Input Parameters
| Name | In | Description |
|---|---|---|
| name | Path |
Required. A string that indicates the name of the metadata field. This value is not case sensitive. |
Table 537: GET Metadata Fields {name} Response Data
| Name | Description |
|---|---|
| ID | An integer indicating the Keyfactor Command reference ID for the metadata field. This ID is automatically set by Keyfactor Command. |
| Name |
A string indicating the name of the metadata field. This name appears in interfaces where you can use metadata, such as certificate details dialogs, alert dialogs, certificate imports and certificate requests. Once this field has a value associated with it for at least one certificate, you cannot change this name. The metadata name field cannot contain spaces; dashes and underscores are supported. |
| Description | A string indicating the description for the metadata field. |
| DataType |
An integer indicating the data type of the metadata field. |
| Hint |
A string indicating a short hint for the metadata field. This hint appears in unpopulated metadata string, integer, big text and date fields on editing interfaces to provide the user with a clue as to what type of data should be entered in the field. This field is only supported for metadata fields with data types string, integer, date or big text. |
| Validation | A string containing a regular expression against which data entered in a string field will be validated. When a user enters information in a metadata field that does not match the specified regular expression, he or she will see the warning message specified in the Message field. For example: ^[a-zA-Z0-9'_\.\-]*@(keyexample\.org|keyexample\.com)$ This regular expression specifies that the data entered in the field must consist of some number of characters prior to the “@” made up only of lowercase letters, uppercase letters, numbers, apostrophes, underscores, periods, and/or hyphens followed by exactly either “@keyexample.org” or “keyexample.com”. This field is only supported for metadata fields with data type string. Tip: If a value is set for a given metadata field at either the template or enrollment pattern level, these take precedence over the system-wide settings in PFX and CSR enrollment requests as follows:
|
| Enrollment |
An integer indicating how metadata fields should be handled on the PFX and CSR Enrollment pages. Tip: If a value is set for a given metadata field at either the template or enrollment pattern level, these take precedence over the system-wide settings in PFX and CSR enrollment requests as follows:
|
| Message |
A string containing a message to present when a user enters information in a metadata field that does not match the specified regular expression (Validation field). Tip: If a value is set for a given metadata field at either the template or enrollment pattern level, these take precedence over the system-wide settings in PFX and CSR enrollment requests as follows:
|
| Options |
An array containing a comma separated list of values that should appear in the field dropdown for multiple choice fields. This field is only supported for metadata fields with data type multiple choice. |
| DefaultValue |
A string containing a default value with which to pre-populate the metadata field for new certificate requests made using PFX or CSR enrollment. Data type of Email will accept a comma separated list of email addresses (limit 100 characters per email address). This field is only supported for metadata fields with data types string, integer, Boolean, or multiple choice. Tip: If a value is set for a given metadata field at either the template or enrollment pattern level, these take precedence over the system-wide settings in PFX and CSR enrollment requests as follows:
|
| AllowAPI |
This is considered deprecated and may be removed in a future release. |
| ExplicitUpdate |
This is considered deprecated and may be removed in a future release. |
| DisplayOrder | An integer indicating the order in which the metadata field should be displayed on pages where the metadata fields are displayed (e.g. PFX enrollment, certificate details). |
| CaseSensitive |
A Boolean for string metadata fields with RegEx Validation defined, that sets the validation for the field to be case-sensitive (true) or not (false). If the user's entry for the metadata field does not match the expected case, the RegEx Message will display. Defaults to false. Tip: If a value is set for a given metadata field at either the template or enrollment pattern level, these take precedence over the system-wide settings in PFX and CSR enrollment requests as follows:
|
An API is a set of functions to allow creation of applications. Keyfactor offers the Keyfactor API, which allows third-party software to integrate with the advanced certificate enrollment and management features of Keyfactor Command. endpoints can be called and results returned. It is intended to be used primarily for validation, testing and workflow A workflow is a series of steps necessary to complete a process. In Keyfactor Command, it refers to the workflow builder, which allows you to automate event-driven tasks such as when a certificate is requested, revoked or found in a certificate store. development. It also serves secondarily as documentation for the API. The link to the Keyfactor API Reference and Utility is in the dropdown from the help icon (
) at the top of the Management Portal page next to the Log Out button.Was this page helpful? Provide Feedback