unexpected difference between create user response and signup response for weak password

I would like to report on unexpected difference between “create user” response and “signup” response for weak password.

We are integrating auth0 as an OAuth2.0 Identity Provider at our Java backend server.
We are using the “create user” management API.

In case the API fails due to the input of our users (weak password, etc…), we would like to present our users with the API message.
However, in case of PasswordStrengthError - it seems that the “create” API doesn’t return detailed description of the password rules while the “signup” API is returning such detailed description.
The “create” API just return “Password is too weak” - so our users are not presented with the required password rules that are defined at our auth0 connection.

Would it be possible to enhance the “create” API so it would return the password rules in case the specified password is too weak ( just like the “signup” API )?

For example:

Management Api create user: /api/v2/users
“error”:“Bad Request”,
“message”:“PasswordStrengthError: Password is too weak”}

SignUp Api: /dbconnections/signup
description={rules={message=At least %d characters in length, format=[6], code=lengthAtLeast, verified=false}], verified=false}
message=‘Password is too weak’,

As it has been more than a few months since this topic was opened, and there has been no reply or further information provided as to the existence of the issue, we are closing this topic. Please don’t hesitate to create a new topic if this issue is still present, we would be happy to work with you to help find a resolution.