Can't create new user trough API without password

[gpredl]

Within NC control panel it's possible to configure 'Send email to new users'. If done so, one can leave password blank when creating new user. Email for activation and password setup will be send to new user.

We'd like to create new users trough the API, without providing password, but email instead.
This is not possible trough the API.

Steps to reproduce

1. POST to /ocs/v1.php/cloud/users with parameters 'userid' and 'email'

Expected behaviour

In control panel we've set up: Send email to new users.
As mentioned in the docs it should be possible to dismiss 'password' and use 'email' instead.
Email should be send to news users to activate account and set password.

Actual behaviour

API responds with 101: Bad request

Server configuration

Nextcloud version 13

[nextcloud-bot]

GitMate.io thinks possibly related issues are #3914 (Can't create a user from GUI with simple passwords), #10333 (Admin can not change user password), #2289 (Admin can't create new user), #4836 (logo alignment issue on new password for new user without password created), and #997 (password policy not applied when creating new user).

[leomelzer]

@gpredl This is now possible (v14) and landed in 41b690e

We discovered an issue with our custom password policy (32 characters) as the length and layout of the auto-generated password is currently hardcoded in the provisioning API.

Instead it should reuse the policy like in the sharing app:

server/apps/sharebymail/lib/ShareByMailProvider.php

Line 216 in 9b9d729

if (!empty($passwordPolicy)) {

Seems like this would require some more work (making this more general and then pulling it in for different apps).

[gpredl]

Some idea about a workaround?
Or is there any way to send the 'Password lost token' to a user by calling the api or something else?

[szaimen]

We don't support creating users without password.

[DylannCordel]

We don't support creating users without password.

Too bad. When authentication is provided by SSO, but users are created by API, we must create user with random password which is worst than creating an user with a blank password which not allow normal auth with it.

Furthermore, it's too bad the API can not reproduce the normal behavior of the web admin interface...

Could you please explain why you don't want to support it ?