Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

wknd tutorial has graphql pre-configured, but its giving forbidden

Avatar

Avatar
Ignite 10
Level 4
TB3dock
Level 4

Likes

34 likes

Total Posts

203 posts

Correct Reply

4 solutions
Top badges earned
Ignite 10
Boost 25
Give Back 25
Validate 10
Validate 1
View profile

Avatar
Ignite 10
Level 4
TB3dock
Level 4

Likes

34 likes

Total Posts

203 posts

Correct Reply

4 solutions
Top badges earned
Ignite 10
Boost 25
Give Back 25
Validate 10
Validate 1
View profile
TB3dock
Level 4

24-03-2021

according to this tutorial, installing the latest wknd site from git, should give you a configured graphql endpoint ready to go.

 

Below we can see that the endpoint is configured, and the vanity url is http://localhost:4502/content/graphql/global/endpoint

 

TB3dock_0-1616622197744.png

 

The tutorial seems to be saying the correct URL to use is http://localhost:4502/content/graphql/global/endpoint.json

 

When I send a simple graphql request to this URL, I get this response:

 

{
"servlet":"org.apache.felix.http.base.internal.dispatch.DispatcherServlet-313d2b89",
"message":"Forbidden",
"url":"/content/graphql/global/endpoint.json",
"status":"403"
}

 

 

Any ideas?  Is it requiring some sort of authentication? If so, how do I disable it (i.e. make it public)

 

 

Accepted Solutions (0)

Answers (1)

Answers (1)

Avatar

Avatar
Boost 100
Level 7
rush_pawan
Level 7

Likes

120 likes

Total Posts

192 posts

Correct Reply

77 solutions
Top badges earned
Boost 100
Validate 1
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Boost 100
Level 7
rush_pawan
Level 7

Likes

120 likes

Total Posts

192 posts

Correct Reply

77 solutions
Top badges earned
Boost 100
Validate 1
Ignite 1
Give Back 5
Give Back 3
View profile
rush_pawan
Level 7

25-03-2021

did you check CORS enablement from OSGI mentioned at bottom of this page https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/g...

 

also, look at logs, you may get some clue there as well!!

 

because for me it works perfectly fine.