Not able to access AEM page using postman GET request | Community
Skip to main content
pradeepd1320668
pradeepd1320668
New Participant
August 19, 2020
Solved

Not able to access AEM page using postman GET request

  • August 19, 2020
  • 2 replies
  • 3517 views

Hi All,

 

I am trying to access AEM page using GET request via Postman tool. I have enabled anonymous access in 'Apache Sling Auhentication Service' still it is not working. Page is opening fine through browser.

Getting below error when accessing via Postman

19.08.2020 12:58:48.556 *INFO* [0:0:0:0:0:0:0:1 [1597822128552] GET /content/test/en/page.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /content/test/en/page.html not found

 

Any help is much appreciated. 

 

Thanks,

Pradeep
 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Nikhil-Kumar

@pradeepd1320668  - Please check for the Authentication of the AEM server in your Postman.
Refer the attachment below: 

2 replies

SundeepKatepally
SundeepKatepally
New Participant
August 20, 2020

 

You need to do 2 things

Option1  -  Anonymous Access 

1) Allow anonymous user in the config "sling authentication service" config.

2) Give read permisions on the content to anonymous user.

 

Option2 - In Post man use Basic authentication. ,where you can give username and password.

 

Option1 is not recommended as you are almost giving the read access without login in author.

 

 

    pradeepd1320668
    pradeepd1320668Author
    New Participant
    August 20, 2020

    Thank you. It worked through postman, i need to implement same in react. I believe there also it will work.

    Nikhil-Kumar
    Nikhil-KumarAccepted solution
    New Participant
    August 19, 2020

    @pradeepd1320668  - Please check for the Authentication of the AEM server in your Postman.
    Refer the attachment below: 

      pradeepd1320668
      pradeepd1320668Author
      New Participant
      August 20, 2020
      It worked. Thank you.
      Terms & ConditionsAccessibility statement

      Loading footer...