The `populate=*` query param not working for `/me` endpoint

[dimonenkov]

Bug report

Required System information

• Node.js version: v16.15.0
• NPM version: 8.5.5
• Strapi version: 4.1.10
• Database: SQLite
• Operating system: Linux

Describe the bug

The populate=* query param for deep nested component fields is not working for /me endpoint.
For example, users/?populate=* or users/1?populate=* are returning deep nested component relations but users/me?populate=* doesn't.

Steps to reproduce the behavior

n/a

Expected behavior

The populate=* query parameter should work for the /me endpoint, just like the other endpoints.

Screenshots

n/a.

Code snippets

n/a

Additional context

n/a

[Nikoxx99]

Also noted this. I review the commit tests and see nothing for this endpoint. Maybe it's not planned to support population for it?

[derrickmehaffy]

confirmed on v4.1.10

[martinomg]

Here are some related threads
https://forum.strapi.io/t/populate-users-permissions-to-get-user-avatar/13701
https://forum.strapi.io/t/how-to-populate-users-strapi-v4/15353

How is severity determined? because this forces either to hard code the /users/me/ endpoint (is not hard but it adds a different treatment for one specific file and endpoint to the code base) or to expose /users/1 endpoint which in some designs is not desirable and even insecure.

Thank you ✌

[fingeg]

Related issue with the user object in the response of the authentication process.
The response of /auth/local does not populate its content.
Don't want to make an additional request after a successful login, just to get the populated content.