Applying Configuration Changes
To update the application configuration using the yaml file, follow these steps:
Copy the template yaml file.
- Edit the properties in the new distribution.config.import.yml file
- Restart the Distribution service with the updated yaml file. This update will propagate to the additional nodes.
Configuration file changes
A snapshot of the last imported configuration state will be saved as
Previous yaml configuration files will be saved as
distribution.config.TIMESTAMP.yml. Up to a maximum of 10 previous configuration states.
Increasing the Header Size (server.max-http-header-size)
The Request header max size can manually be increased to prevent receiving an HTTP 400 message when signing into Distribution with SSO.
For this change to take effect, each distribution node in the cluster must be restarted. Start with rebooting the first node one on which the config file is installed and proceed to the remaining Edge nodes.
Setting the User Scoped Token for Distribution to Source Artifactory
From Distribution 2.13.2, user permissions will be enforced when distributing to the source JPD. The permissions are as follows:
To distribute release bundles: Only users with read and deploy permissions on the target repositories can successfully complete a distribution process to the source Artifactory (in this case the JPD acts as the target JPD).If this type of user (non-admin) tries to distribute to a target repository that does not exist, they will receive an error message.
To delete release bundles: Only users with delete permission for the target repository can delete these bundles.
Once you upgrade your Distribution version to this release, the user scoped token becomes the default configuration for Distribution.
Requirements and Limitations
This feature requires you to have Artifactory 7.40.x and later installed for the source Artifactory (not target). Otherwise, even if you have set this configuration to true, it will revert to the current setting.
This setting is relevant only for distributing to the source Artifactory.
Deploying Your GPG Key on the Source Artifactory
Distribution will trigger the source Artifactory to clone the contents of signed release bundles into an isolated
release-bundles repository. To allow this, you need to deploy the GPG Key that is used in each of your Artifactory Edge nodes to the source Artifactory service.
For more details, refer to Setting a GPG Key.
For more details on additional required configurations, refer to configuring Distribution.