Artifactory Configuration Files

The global Artifactory configuration file is used to provide a default set of configuration parameters.

The Global Configuration Descriptor file is located in $JFROG_HOME/artifactory/var/etc/artifactory/artifactory.config.xml and is loaded by Artifactory at initial startup. Once the file is loaded, Artifactory renames it to artifactory.config.bootstrap.xml and from that point on, the configuration is stored internally in Artifactory's storage. This ensures Artifactory's configuration and data are coherently stored in one place making it easier to back up and move Artifactory when using direct database backups. On every startup, Artifactory also writes its current configuration to $JFROG_HOME/artifactory/var/etc/artifactory/artifactory.config.latest.xml as a backup.

At any time, the default configuration can be changed in the Artifactory UI Administration module.

There are two ways to directly modify the Global Configuration Descriptor:

Modifying Configuration Using the UI

You can access the Global Configuration Descriptor in the Administration module under Artifactory | Advanced | Config Descriptor. There you can modify the file's contents directly or copy the contents from the entry field.

Modifying Configuration Using the REST API

You can retrieve or set the global configuration by sending a GET or POST request to http://<host>:<port>/artifactory/api/system/configuration . For example:

curl -u admin:password -X GET -H "Accept: application/xml" http://localhost:8081/artifactory/api/system/configuration
curl -u admin:password -X POST -H "Content-type:application/xml" --data-binary @artifactory.config.xml http://localhost:8081/artifactory/api/system/configuration

Bootstrapping the Global Configuration

You can bootstrap Artifactory with a predefined global configuration by renaming the $JFROG_HOME/artifactory/var/etc/artifactory/artifactory.config.latest.xml file containing the Artifactory configuration descriptor to $JFROG_HOME/artifactory/var/etc/artifactory/artifactory.config.import.xml.

From Artifactory 7.49.3, you would also need to rename the file $JFROG_HOME/artifactory/var/etc/artifactory/artifactory.repository.config.latest.json to $JFROG_HOME/artifactory/var/etc/artifactory/artifactory.repository.config.import.json.

If Artifactory detects this file at startup, it uses the information in the file to override its global configuration. This is useful if you want to copy the configuration to another instance of Artifactory.

Security Configuration Descriptor contains Artifactory security configuration information.

Bootstrapping the Security Configuration

Artifactory stores all security information as part of its internal storage.You can bootstrap Artifactory with a predefined security configuration by creating a $JFROG_HOME/artifactory/var/etc/artifactory/security.import.xml file containing the Artifactory exported security configuration information.

If Artifactory detects this file at startup, it uses the information in the file to override all security settings. This is useful if you want to copy the security configuration to another instance of Artifactory.

Modifying Security Using the REST API

Modifying the Security Configuration Descriptor Using the REST API has been deprecated.

Artifactory provides a flexible mechanism to manage content type/MIME Type. You can define system-wide MIME types for common usage, but you can also overwrite the MIME types for specific files as needed. You can find the list of default MIME types in $JFROG_HOME/artifactory/var/etc/artifactory/mimetypes.xml and can be edited in order to add, remove or change MIME types.

If a file has an extension that is not supported by any of the MIME types, or does not have an extension at all, Artifactory will use the default MIME type of application/octet-stream. To determine an artifact's MIME type, Artifactory compares its extension with the those in the mimetype.xml file, and applies the MIME type of the first extension that matches.

MIME Type Attributes

Each MIME type have the following attributes.

The following example shows a mimetype.xml file.

<mimetypes version="4">
    <mimetype type="text/plain" extensions="txt, properties, mf, asc" viewable="true" syntax="plain"/>
    <mimetype type="text/html" extensions="htm, html" viewable="true" syntax="xml"/>
    <mimetype type="text/css" extensions="css" viewable="true" syntax="css"/>
    <mimetype type="text/xsl" extensions="xsl" viewable="true" syntax="xml"/>
    <mimetype type="text/xslt" extensions="xslt" viewable="true" syntax="xml"/>
    <mimetype type="text/x-java-source" extensions="java" viewable="true" syntax="java"/>
    <mimetype type="text/x-javafx-source" extensions="fx" viewable="true" syntax="javafx"/>
</mimetypes>

For the example, from the extensions parameter in the above mimtypes.xml file sample we can conclude that:

Make sure you restart Artifactory for your changes to take affect.

Setting Content-Type During Download

Using Artifactory, when downloading files you can override the Content-Type HTTP header by setting the artifactory.content-type property. If the artifactory.content-type property is not explicitly set, Artifactory will use the default mechanism of matching the artifact name extension to the extensions in the mimtypes.xml file to apply the Content-Type.

This feature is only available with Artifactory Pro.

Rather than configuring properties in the JVM runtime configuration of the hosting container, you can edit $JFROG_HOME/artifactory/var/etc/artifactory/artifactory.system.properties file and restart Artifactory.

The Artifactory system properties are documented within this file.

Since these settings impact the entire container VM, we recommend using this feature primarily for specifying Artifactory-related properties only (such as changing the database used by Artifactory, etc.).