Allow "READ" operations using the Adobe Experience Manager Assets HTTP API without required "WRITE" access - Status changed to: Investigating

[#1]

Request for Feature Enhancement (RFE) Summary:	Allow "READ" operations using the Adobe Experience Manager Assets HTTP API without requiring "WRITE" access
Use-case:	Users who are not given write access should still be able to fetch asset data using the Assets HTTP API even if they don't have WRITE access
Current/Experienced Behavior:	Right now, if a user only has read-only access, he or she is not able to use the read functions of the assets API
Improved/Expected Behavior:	Provide the flexibility to be able to use the API while only having a read access
Environment Details (AEM version/service pack, any other specifics if applicable):	AEMaCS
Customer-name/Organization name:	Prequire
Screenshot (if applicable):
Code package (if applicable):

[#2]

@mikeetiuPH  I did not understand. is it a post mistake ?

Users who are not given a write-only access should still be able to fetch asset data using the Assets HTTP API even if they don't have WRITE access

You mean to say read-only ? 

[#3]

@Jagadeesh_Prakash  - updated., pls check

[#4]

@mikeetiuPH 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference ASSETS-15114. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

[#5]

Hi @mikeetiuPH, thanks for the report. This should be resolved in AEM Cloud Service releases > 9145. Could you please check and verify that it's working for you now? 

If not, could you please provide more details as to what operations (e.g. example requests) are failing so we can diagnose further. 

[#6]

@klcodanr  Cool thank you! We'll check it out!

[#7]

@mikeetiuPH, Marking this as delivered as per @klcodanr's comments.