Api-test. Clean up creating test users via ocs endpoint

[ScharfViktor]

for our apiTest we have 3 option to create user/group using:

• graph endpoint(TEST_WITH_GRAPH=true)
• ldap (need for reva "TEST_WITH_LDAP": "true")
• ocs endpoint - not possible now ([full-ci] Remove glauth and accounts services #3685)

ocis doesn't create users/groups using the ocs endpoint after we switch to graph.
mobile client doesn't support admin options
we don't have any tests for creating or deleting users in ocis using ocs except https://github.com/owncloud/ocis/tree/master/tests/acceptance/features/coreApiAuthOcs

@SwikritiT and me suggest to:

• delete all ocs steps (CRUD users/group) from Provisioning.php Api-test. Clean up creating test users via ocs endpoint #6998 (comment)
  - we are deleting all the ocs steps (CRUD users/group) because CRUD operation related to users/group through ocs are not possible anymore. Please refer to following PR's/issues for further information : [docs-only] beta-testplan: Adjust curl examples to use graph instead of accounts/ocs #3820, [full-ci] Remove glauth and accounts services #3685, Use GraphAPI for creating/deleting users and groups in acceptance test #3167, [tests-only][full-ci] run core acceptance tests with the Graph API #3404
• delete env TEST_WITH_GRAPH=true and use graph api by default will be done in delete env TEST_WITH_GRAPH=true and use graph api by default #8276 @amrita-shrestha

[individual-it]

duplicate of #6729 ?

[SwikritiT]

In addition to what's written here, we have some open issues related to ocs provisioning api like #2729, which might no longer be relevant, we can go through the issues to determine if it's relevant and close them if not.

[S-Panta]

The test codes that involve user creation (single or in groups) have been moved so that they now use graph API only and the PR is merged. #7019. The following tasks left to clean are:

master

• user creation (single or in groups) [tests-only][full-ci] refactoring user creation Given steps from provisioning into GraphContext #7019
• Deleting the user [tests-only][full-ci] refactoring the user delete code from ocs to graphapi #7020
• Adding a user to the group [tests-only][full-ci] refactoring user addition to group to graphapi #7360
• remove the user from the group [tests-only][full-ci] refactoring user remove from group test code  #7380
• creating the group @nabim777 [tests-only][full-CI] Remove OCS endpoint for group creation #7864
• deleting the group @nabim777 [tests-only][full-ci] Restructure the steps implementation for group delete to use graph API endpoint #8006
• setting the user quota [tests-only][full-ci] adding user quota using graph api instead of Provisioning api #7000 @S-Panta

backport to stable-4.0

• user creation (single or in groups) [https://github.com/[tests-only][full-ci] refactoring user creation Given steps (#7019) #7259]
• Deleting the user [https://github.com/[tests-only][full-ci] refactoring the user delete code from ocs to graph api #7679]
• Adding a user to the group [tests-only] [full-ci] backporting the PR related to user addition to group to graphapi #7545
• remove the user from the group [tests-only][full-ci] use graph api to remove remove user from group #7837
• creating the group [tests-only][full-ci][backport] Remove OCS endpoint for group creation #8043

[S-Panta]

@saw-jan can you add more if there are any left to do regarding this refactoring task?

[pascuflow]

Newbie here, moved from OCS to OCIS and trying to create a user via api, using Docker with ocis 4.0.0+f5f11e0bd and web client version 8.0.0-alpha.4. Used to do it with OCS like:

    let storageData = new FormData();
    storageData.append("userid", email);
    storageData.append("password", password);

    await axios.post(storageUrl + "/ocs/v1.php/cloud/users", storageData, {
      auth: {
        username: process.env.ADMIN_USERNAME,
        password: process.env.ADMIN_PASSWORD,
      },
      headers: storageData.getHeaders(),
    });

Do I need to do any setup before running the docker ocis image? What endpoint to call?

Thanks

[saw-jan]

oCIS 4.0.0 uses graph API for user/group provisioning. The request looks like this:

curl -XPOST "https://localhost:9200/graph/v1.0/users" \
-d'{"displayName":"Alice Hansen","mail":"alice@example.org","onPremisesSamAccountName":"alice","passwordProfile":{"password":"1234"}}' \
-u admin:admin

[pascuflow]

Tried that on localhost and behind a proxy with valid cert, got 401 for both, do I need an access token and if so how do I obtain one? Or perhaps disable it and allow basic auth?

curl -k -i -XPOST "https://localhost:9200/graph/v1.0/users" -d'{"displayName":"Alice Hansen","mail":"alice@example.org","onPremisesSamAccountName":"alice","passwordProfile":{"password":"1234"}}' -u admin:password

HTTP/1.1 401 Unauthorized
Www-Authenticate: Bearer realm="localhost:9200", charset="UTF-8"
X-Request-Id: 1ab3afc5569f/4KU04OtP27-000292
Date: Fri, 27 Oct 2023 11:43:28 GMT
Content-Length: 0

EDIT: Got it to work by PROXY_ENABLE_BASIC_AUTH to true

[saw-jan]

Yeah, by default ocis doesn't allow basic auth. we need to enable basic-auth using PROXY_ENABLE_BASIC_AUTH.