Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Querybuilder API with AEMaaCS

Avatar

Level 1

Hello-

I'm using the Querybuilder API to retrieve my AEM sites pages filtering with the path query parameter. I'm wondering if the Querybuilder API is also available for the cloud version, AEMaaCS. I am aware of the headless ability but I'm not able to follow the documentation on a simple endpoint like Querybuilder to get this same data for AEMaaCS.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@adwilliams  it is a normal way of creating a local user with in environment. 

 

create local user from security--->users

Jagadeesh_Prakash_0-1683606296142.png

 

And set permissions to that local user in permissions tab

Jagadeesh_Prakash_1-1683606349767.png

 

you can try login from SIGN IN LOCALLY

Jagadeesh_Prakash_2-1683606379439.png

 

View solution in original post

5 Replies

Avatar

Community Advisor

@adwilliams  May be i am unable to understand the question here but i am able to run the query builder in AEMaaCS. but it will return only the JSON structure you can change the query parameters and update the query. 

 

 http://<AEMCS-URL>/bin/querybuilder.json?type=cq:Page&path=/content&limits=-1 

 

Avatar

Level 1

Hi @Jagadeesh_Prakash ,

I'm asking specifically because the two documentation pages mentioned different authentication methods. 
For AEMaaCS it seems we need JWT today and will require OAuth in the future versus for Querybuilder for a Cloud SDK just uses basic authentication.

Avatar

Community Advisor

@adwilliams Insted of generating JWT token. You can have a local user created in AEMaaCS environment and give him all necessary access and use that users for basic authentication. 

Avatar

Level 1

Thank you! do you have instructions on how to make a local user for AEMaaCS?

Avatar

Correct answer by
Community Advisor

@adwilliams  it is a normal way of creating a local user with in environment. 

 

create local user from security--->users

Jagadeesh_Prakash_0-1683606296142.png

 

And set permissions to that local user in permissions tab

Jagadeesh_Prakash_1-1683606349767.png

 

you can try login from SIGN IN LOCALLY

Jagadeesh_Prakash_2-1683606379439.png