How can we install JFrog Xray with our own application user instead of user and group xray on redhat standalone server?
xray and rabbitmq user and groups are created while installing JFrog Xray. But we need that to be owned and executed with our own user and group. How can we do that?
Why is it necessary to run the Jfrog Xray installation script under root or as sudo user?
The general answer for all of them is the same: Your points are valid and the current situation is suboptimal. The xray user shouldn't be hardcoded for our microservices and root shouldn't be required for installing 3rd-party services, especially if the user installs those by themselves. We are working on fixing all that.
I am with JFrog, the company behind jfrog-xray and artifactory, see my profile for details and links.
Related
I'm doing a helm install of JFrog XRay and I'm running into a snag. We have Artifactory installed internally using a company self-signed cert and XRay won't come up because of it. The router component fails with 'certificate signed by unknown authority'. How do I get past this issue? Is there a method for injecting the root cert into the container?
I assume this is Xray 3.x installation connecting with Artifactory 7.x and if som based on this wiki, you need to pass the self-signed certificate under the location $JFROG_HOME/xray/var/etc/security/keys/trusted directory and as this is a helm based install and I think a k8 secrets should be created and passed in that mentioned location. Also, refer to this github.
As Xray is written in Go, you can pass the self-signed certificates by placing them in /etc/ssl/certs/ and restarting Xray.
I am using on-prem JFrog Artifactory to hold maven artifacts. I have a need to use this artifactory to hold my app's docker images. So I tried creating a new docker repository but it showed me docker type as disabled. When I am looking around people are suggesting to use JFrog Container Registry.
My question is, can't I create a docker repository in my existing artifactory, does it require any plugin etc. to be downloaded to add this functionality in existing artifactory ? And how to enable that docker repository option while trying to create a new repository ?
Seems like you are using the Artifactory OSS version and not the Artifactory pro version, Artifactory OSS is limited as this an open-source version for the Maven-based projects. As everyone recommends you can make use of the JFrog container registry which is free to use application to handle the Docker registries.
Otherwise you can utilize the FREE Cloud Artifactory to handle all the different repositories in a single Artifactory instance.
I have JFrog Artifactory http://organization.com/artifactory/ with read access. I can download individual artifacts let's say gulp-git-2.8.0.tgz using native browser.
Now, I have created local JFrog Artifactory http://localhost.com:8081/artifactory/ in machine and it does not have any artifacts.
I am trying to fetch my organizations artifacts lets say of npm package http://organization.com/artifactory/npm/ into my local artifactory http://localhost:8081/artifactory/npm/
Since it has many artifacts and I cannot do it manually of download from organization server and deploying it to my local server.
Is there anyway that I can fetch only the required package let's say npm to my local server? Or is there anyway to replicate my organization's package using read access into my local server?
Thanks in advance.
If you have Admin permissions to the source Artifactory you can setup Push replication or to perform a Repository Export.
Without Admin permissions, you can:
Setup Pull Replication.
Use the JFrog CLI in order to download entire repository content, and then upload it in the same structure.
Does AWS codedeploy run as any specific user profile on Windows servers?
I am trying to run a jfrog.exe cli to download from a remote Artifactory repository, using a prebuilt user ID and password which is dependent on ~/users/{user id}/.jfrog/jfrog-cli.conf
How would codedeploy be able to source a .jfrog/jfrog-cli.conf ?
The CodeDeploy agent is configured as service to use the SYSTEM account as logon identity. Because of that all processes execute as the SYSTEM user. As a word of caution, the process cmd and powershell processes launched by agent are in 32bit mode. This is important to understand because
Powershell 32bit and 64bit have differences, especially when there is a dependency to installed modules.
Some things are different with the SYSTEM user. For example the temp directory is not the same as with for every other user.
Knowing this helps a lot when trying to troubleshoot.
CodeDeploy now only support repo in S3 or Github. Where does your repo exists?
Bamboo supports shared credentials.
I would like to use these shared credentials to commit tags to git using the artifactory maven addon.
According to this ticket: https://www.jfrog.com/jira/browse/BAP-189 it should work.
I do however not know where to configure it.
We are using bamboo 5.14.3.1
Artifactory plugin 2.1.0
Was this feature removed?