provisioning API report is incomplete when user name casing is not exact

[jnweiger]

Seen in 10.9.0 beta1

In #36139 (comment) @phil-davis reported that quota details are missing, when unexpected upper case is used on a username.
This is still reproduced in 10.9.0 beta1

[JammingBen]

Tried to reproduce this, but everything looks fine for me, regardless of the casing. One thing to notice though: Curling a user that has never logged in (curl -u admin:admin http://172.17.0.1:8080/ocs/v2.php/cloud/users/uu1) results in missing quota details - this is expected IMO.

@phil-davis @jnweiger Could you please re-evaluate? Am I missing something?

[phil-davis]

Could you please re-evaluate? Am I missing something?

I can reproduce, and I have a fix coming... Making tests to confirm it.

[phil-davis]

See PR #39586

[JammingBen]

Has been merged -> closing.