Deploying using access_token does not yield same result as with curl, namely in the "Deployed By" Field in Artifactory

[zshehadeh2]

Im using version 2.7.0....

When I do:
curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
-T text_example.txt
"https:/my-artifactory.mydomain.com/artifactory/path/to/your/text_example.txt"

It correctly used my access token:

Using the new way of authentication, leads to my username in the "Deployed by" field as opposed to the token name.
return Artifactory(
self.url,
access_token=token,
verify=self.verify,
cert=self.cert,
)

However, interestingly using the old way with the token, and using the token username, it works as expected. You can get the token username by decoding your JWT and looking for the section that comes after /users/

return Artifactory(
self.url,
auth=(user, token),
verify=self.verify,
cert=self.cert,
)

[zshehadeh2]

https://requests.readthedocs.io/en/latest/user/authentication/#netrc-authentication

Your usage of requests library is defaulting to using netrc when using access_token since auth is None

See more:
https://stackoverflow.com/questions/60358216/python-requests-post-request-dropping-authorization-header

[zshehadeh2]

Maybe decode the JWT token in your code and get the username for the access_token and fill in the auth field with (username, token) tuple