Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delivery Api Query is not returing any results if Authorization Bearer header is added #17560

Open
mcl-sz opened this issue Nov 17, 2024 · 1 comment
Labels

Comments

@mcl-sz
Copy link
Contributor

mcl-sz commented Nov 17, 2024

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

13.5.2

Bug summary

When a Authorization Bearer header is added to a Delivery Api Query, no results are returned. The content is not protected with member access.

image
image

When the Autorization Bearer header is removed, all children are returned.

image
image

Specifics

/umbraco/delivery/api/v2/content?fetch=children:{guid-of-parentnode}&take=10&skip=0&fields=properties[$all]

Steps to reproduce

Create a Delivery Api fetch request and add a Authorization Bearer header with a access token to a node that has no member access protection.

/umbraco/delivery/api/v2/content?fetch=children:{guid-of-parentnode}&take=10&skip=0&fields=properties[$all]

Expected result / actual result

The Delivery Api should return content if a Authorization Bearer header is added.

Copy link

Hi there @mcl-sz!

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 🤖 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant