The advanced settings for a remote repository configure network access behavior, cache management and several other parameters related to remote repository access.
To access the advanced settings, in the Edit Remote Repository screen select the Advanced tab.
|The username that should be used for HTTP authentication when accessing this remote proxy.|
|The password that should be used for HTTP authentication when accessing this remote proxy.|
|If your organization requires you to go through a proxy to access a remote repository, this parameter lets you select the corresponding Proxy Key.|
For more details on setting up proxies in Artifactory please refer to Managing Proxies.
When working on multi-homed systems, this parameter lets you specify which specific interface (IP address) should be used to access the remote repository.
The time that Artifactory waits (for both a socket and a connection) before giving up on an attempt to retrieve an artifact from a remote repository.
A custom set of parameters that should automatically be included in all HTTP requests to this remote repository.
Lenient Host Authentication
|When set, allows using the repository credentials on any host to which the original request is redirected.|
|When set, the repository will allow cookie management to work with servers that require them.|
Using Oracle Maven Repository
To use Oracle Maven Repository:
- Set your Oracle credentials in Username and Password of the Remote Credentials
- Set Lenient Host Authentication
- Set Enable Cookie Management.
Artifactory stores artifacts retrieved from a remote repository in a local cache. The Cache Settings specify how to manage cached artifacts.
Caching Maven artifacts
Caching for Maven artifacts is only applicable to snapshots since it is assumed that releases never change.
Unused Artifacts Cleanup Period
Many cached artifacts in Artifactory remote repository storage are actually unused by any current projects in the organization. This parameter specifies how long an unused artifact will be stored before it is removed. A value of 0 means that the artifact is stored indefinitely.
Removing unused artifacts
Unused artifacts are not removed immediately upon reaching this timeout, but only on the next invocation of cleanup.
Retrieval Cache Period
Defines how long before Artifactory checks for a newer version of a requested artifact in a remote repository.
This setting refers to artifacts that may change (e.g. snapshots, metadata files etc.). Note that most artifacts that are downloaded do not change (e.g. release versions), therefore this setting has no effect on them.
Assumed Offline Period
In case of a connection error, this parameter specifies how long Artifactory should wait before attempting an online check in order to reset the offline status.
Missed Retrieval Cache Period
If a remote repository is missing a requested artifact, Artifactory will return a "404 Not found" error. This response is cached for the period of time specified by this parameter. During that time, Artifactory will not issue new requests for the same artifact.
"Zapping" a cache means forcing the Retrieval Cache Period and Missed Retrieval Cache Period to time out. To "zap" a cache, in the Artifacts module Tree browser,
Select the repository cache you wish to "zap" and click Zap caches in the right-click menu or Actions drop-down menu.
Select Property Sets
Defines the property sets that will be available for artifacts stored in this repository.
|If set, Artifactory ignores this repository when trying to resolve artifacts. The repository is also not available for download or deployment of artifacts.|
Allow content browsing
When set, allows Artifactory users to browse the internal contents of archives (for example, browsing specific Javadoc files from within a Javadoc archive.
When archive browsing is allowed, strict content moderation should be employed to ensure malicious users do not upload content that may compromise security (e.g. cross-site scripting attacks)
Store artifacts locally
When set, Artifactory artifacts from this repository will be cached locally. If not set, direct repository-to-client streaming is used.
When might you use direct repository-to-client streaming?
If your organization has multiple servers connected over a high speed LAN, you may have one instance of Artifactory caching data on a central storage facility with additional instances of Artifactory running on other servers. In this case, it makes sense for the additional instances of Artifactory to act as satellite pass-through servers rather than have them duplicate the cached data within their own environments.
|When set, synchronizes properties of artifacts retrieved from a remote instance of Artifactory.|
|If set, the configuration details of this repository are shared with remote clients (e.g. other Artifactory servers) and can be imported by them. For example, this can be useful if your organization maintains several instances of Artifactory, and you want to share remote repository configurations between them.|
For details, please refer to Shared Repository Configurations.