Support Artifactory Access Tokens for CI Integration

Hi,

I have made use of Artifactory access tokens for uploads interactively by doing a conan user and pasting in the encrypted password.

But when I run the build in a docker container, I would prefer to use the authentication header instead of a specific user. I could store it in a file or pass it on the command line or an environment variable. My workaround is to build the docker image with a .conan/.conan.db resulting from having done the conan user, above.

This would take some doing to affect the HTTP headers, but it would be really nice for CI pipelines.

So this would be ideal:

conan upload --auth-file=ci_upload.tok ...
conan upload --auth-tok="32984723938sfkajshu6*#82981234"...

[tamboril]

OK. I think that’s a good solution. Thanks.

[lasote]

It doesn’t work like that. The artifacts.properties only set custom properties for PUT requests. A conan upload contains two requests, the first is calling the conan server (or artifactory) to authorize the upload by generating an internal temporary token, the second is the PUT request and is only a signed url, so authentication can’t be managed with artifacts.properties.