New message text here

@chilly-king-10285 Above solution is not correct,please there is any alternative?

I apologize for the confusion earlier. Based on the provided extracts, you can check the validation errors for password settings during the user settings update process. When a user attempts to update their password, Kratos will validate the new password according to the configured password policy. Possible validation errors include not providing a password or providing a password that doesn't match the password policy. Here's an example of a validation error message for a missing password:

json {   "id": 4000001,   "text": "length must be >= 1, but got 0",   "type": "error" }

And here's an example of a validation error message for a password found in data breaches:

json {   "id": 4000005,   "text": "The password can't be used because the password has been found in data breaches and must no longer be used.",   "type": "error",   "context": {     "reason": "the password has been found in data breaches and must no longer be used."   } }

These examples are taken from the [User Settings and Profile Updates](https://www.ory.sh/docs/kratos/self-service/flows/user-settings) section of the Kratos documentation. Keep in mind that the specific validation rules depend on your Kratos configuration. To check the exact validation rules, you would need to examine your Kratos configuration file.