System.ArgumentNullException: Value cannot be null. (Parameter 'user')

[PeterKvayt]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

10.8.7

Bug summary

If you are not logged in in umbraco backoffice and trying to get resource by url: "domain.com/umbraco/backoffice/umbracoapi/content/GetById?id=1451", you will get System.ArgumentNullException: Value cannot be null. (Parameter 'user').

I think there is something wrong with this code, look at signature. IUser is nullable and at the same time there is a null check.

I think there is should be non nullable IUser or logic with nullable IUser.

Specifics

No response

Steps to reproduce

1. Create some content
2. Logout from backoffice
3. Try to get this content useing following link: "domain.com/umbraco/backoffice/umbracoapi/content/GetById?id=your content id"
4. Look at logs

Expected result / actual result

Expected result: there is no error "System.ArgumentNullException: Value cannot be null. (Parameter 'user')" in logs. Maybe more suitable is to handle this case with 404 or 401 status code response and there is should be consistent signature for CheckPermissions method.

Actual result: there is "System.ArgumentNullException: Value cannot be null. (Parameter 'user')" error in logs

---

This item has been added to our backlog AB#46947

[github-actions]

Hi there @PeterKvayt!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[NguyenThuyLan]

I was able to reproduce it on v13.5.2