Need help with other JFrog products?
Direct modification of the global configuration descriptor is an advanced feature, and if done incorrectly may render JFrog Container Registry in an undefined and unusable state. We strongly recommend backing up the configuration before making any direct changes, and taking great care when doing so.
Modifying Configuration Using the UI
You can access the Global Configuration Descriptor in the Admin module under 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 JFrog Container Registry with a predefined global configuration by creating an
$ARTIFACTORY_HOME/etc/artifactory.config.import.xml file containing the JFrog Container Registry configuration descriptor.
If JFrog Container Registry 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 JFrog Container Registry.
After you have restart and JFrog Container Registry did the import, the old file
$ARTIFACTORY_HOME/etc/artifactory.config.import.xml will be moved to a file called
Security Configuration Descriptor
You can modify the Security Configuration Descriptor Using the REST API.
Direct modification of the security descriptor is an advanced feature, and if done incorrectly may render JFrog Container Registry in an undefined and unusable state. We strongly recommend backing up the configuration before making any direct changes, and taking great care when doing so.
Modifying Security Using the REST API
You can retrieve or set the security configuration by sending a GET or POST request to
http://<host>:<port>/artifactory/api/system/security. For example:
curl -u admin:password -X GET -H "Accept: application/xml" http://localhost:8081/artifactory/api/system/security curl -u admin:password -X POST -H "Content-Type: application/xml" --data-binary @security.xml http://localhost:8081/artifactory/api/system/security
You must supply a user with Admin privileges to modify the security descriptor through the REST API
Bootstrapping the Security Configuration
JFrog Container Registry stores all security information as part of its internal storage.You can bootstrap JFrog Container Registry with a predefined security configuration by creating an
$ARTIFACTORY_HOME/etc/security.import.xml file containing the JFrog Container Registry exported security configuration information.
If JFrog Container Registry 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 JFrog Container Registry.
Content Type/MIME Type
JFrog Container Registry 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. The list of default MIME types can be found in
$ARTIFACTORY_HOME/etc/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, JFrog Container Registry will use the default MIME type of
application/octet-stream. To determine an artifact's MIME type, JFrog Container Registry 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 may have the following attributes:
|The MIME type unique name (mandatory)|
|A comma separated list of file extensions mapped to this MIME type (mandatory)|
|True if this MIME type should be indexed for archive searching (valid only for supported archive files)|
|True if this MIME type is a browsable archive|
|True if this MIME type can be viewed as a text file inside JFrog Container Registry UI|
|The UI highlighter syntax to for this MIME type (only relevant if this is a |
|The css class of a display icon for this mime type|
<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 example, from the extensions parameter in the above
mimtypes.xml file sample we can conclude that:
application/octet-streamMIME type since "
doc" is not included in any of the other MIME types).
IMPORTANT: Make sure you restart JFrog Container Registry for your changes to take affect.
|Some of the Mime-Types specified in |
Setting Content-Type During Download
Using JFrog Container Registry, when downloading files you can override the
Content-Type HTTP header by setting the
artifactory.content-type property is not explicitly set, JFrog Container Registry 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. Ori YitzhakiTeaser|?
Rather than configuring properties in the JVM runtime configuration of the hosting container, you can edit
$ARTIFACTORY_HOME/etc/artifactory.system.properties file and restart JFrog Container Registry.
The JFrog Container Registry system properties are documented within this file.
Since these settings impact the entire container VM, we recommend using this feature primarily for specifying JFrog Container Registry-related properties only (such as changing the database used by JFrog Container Registry, etc.).
Setting properties in
Do not confuse these setting with those in the
Logging Configuration Files
JFrog Container Registry provides you with a
binarystore.xml file so that you can configure the specific storage solution used in your system. For details please refer to Configuring the Filestore.