user creation

[nauni77]

Hello,
I want to use the Artifactory API to manage users, groups, repositories and permissions. With the older instance 7.77.7 this works as expected:

    test_user = NewUser(name="tester123", email="tester123@my-domain.de", password=SecretStr("tester!123"))
    response: UserResponse = test_client.users.create(test_user)
    logger.info(f"create user response: {response}")

Result:

2026-03-16 12:04:26.961 | INFO     | tests.artifactory.test_user_management:test_00_manual_check:72 - create user response: name='tester123' admin=False profileUpdatable=True disableUIAccess=False internalPasswordDisabled=False groups=['readers'] email='tester123@my-domain.de' lastLoggedIn=None realm='internal' offlineMode=False

But if I switch to the new Artifactory (7.133.10) the creation of a user fails with an error:

requests.exceptions.HTTPError: 400 Client Error

I searched the Artifactory API for the corresponding API request to check if something changed. But I can't find a possible request to solve this - only a possibility to retrieve the details of a user:

https://docs.jfrog.com/artifactory/reference/getuserdetails

Can you help? Is the update/creation removed from the Artifactory API?

Best regards, Oli

[anancarv]

Hey @nauni77 ,

Sorry for the late answer. The root cause is that PyArtifactory is using the deprecated Security API (/artifactory/api/security/users) instead of the new Access API (/access/api/v2/users).

As documented, starting with Artifactory 7.49.3, user management was moved from Artifactory to the JFrog Access service. The old Security API may:

• Return 400 errors for previously valid requests
• Have stricter validation
• Be missing features
• Eventually be fully removed

Contributions are welcome. Feel free to create a PR with this change

[nauni77]

Hallo, thanks for your answer. Now I saw the new API in the documentation:
https://docs.jfrog.com/integrations/docs/openapi-specifications

Is there any Python library supporting the current JFrog API? Or is someone changing this project to the new API?

Thanks in advance, Oli

[nauni77]

Hello, hello @anancarv ,
I created a branch and implemented some of the new API.

I understand that I check some logic of my code by mocking data and requests. For example, if the correct exception is thrown.

But if I want to verify that a repository is created or exists, it would be much more useful to check against a running Artifactory with his real API. Is there any possibility to run Artifactory Pro without a license (supporting the API)? Maybe just for 1 hour/day to execute the checks. After this timespan the Artifactory can stop working, and we can create a new one for the next tests.

Or perhaps there is some developer license for this topic?

[anancarv]

Hi @nauni77 ,
Unfortunately, I don't have an active JFrog license, which means I can't test against a live Artifactory instance to verify whether the API changes. If you're using Artifactory in your company, they may be able to provide you with a test license or a staging environment to validate the API changes.

[nauni77]

Hi @anancarv, we have Artifactory licenses at my company, but I can't commit changes and check the results here in github/your project. Extending your project should result in code and tests that are executable here at this environment. Or at least on everybody's development environment.

For now I can just take my tests and run these against our Artifactory instance. I'm just searching for a solution that works for everybody who wants to join your project and help to improve. For now I can just run the tests inside our company.

[anancarv]

Hi @anancarv, we have Artifactory licenses at my company, but I can't commit changes and check the results here in github/your project. Extending your project should result in code and tests that are executable here at this environment. Or at least on everybody's development environment.

For now I can just take my tests and run these against our Artifactory instance. I'm just searching for a solution that works for everybody who wants to join your project and help to improve. For now I can just run the tests inside our company.

That's fine for me, as long as you run the tests on your instance and validate that it works properly.
Regarding the unit tests in this project, you can mock the API results, as it is already done in the lib. Indeed, we use a dedicated lib to mock the API response.