Skip to main content
Question

JSON reader vs Feature Reader - cannot get the feature reader to work


tris_w
Contributor
Forum|alt.badge.img+6

Has anyone had success with using the Feature Reader to read JSON from an HTTPS call? I am trying to read a JSON string from an API into FME for processing. It works great when I use the "JSON Reader" (standalone reader). But I need to do some processing steps before it so trying to do the same thing using the Feature Reader transformer (reading JSON). I am having no success with the Feature Reader for reading any JSON strings. Every time I get the same error:

Received HTTP response header: 'HTTP/1.1 401 Unauthorized'

Configuration is the same in both the JSON reader and the Feature Reader transformer, including username/passwords, its using Basic authentication.

Any tips would be appreciated.

3 replies

trentatsafe
Safer
Forum|alt.badge.img+6
  • Safer
  • October 15, 2020

Hello @tris_w​ 

Do you have a workspace you could share with the URL + Credentials? If unable to share on the forums, I could create a case for this. As it would help us figure out if there is a difference in the request we are making between the FeatureReader and the JSON Reader.

 


tris_w
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • October 16, 2020
trentatsafe wrote:

Hello @tris_w​ 

Do you have a workspace you could share with the URL + Credentials? If unable to share on the forums, I could create a case for this. As it would help us figure out if there is a difference in the request we are making between the FeatureReader and the JSON Reader.

 

Thanks Trent, yes I have found a different json source that I can share credentials with you. It uses an API key instead of user/password but its the same issue. The JSON reader works fine, but the exact same URL in the feature reader gives a 403 forbidden error. whats your email?


trentatsafe
Safer
Forum|alt.badge.img+6
  • Safer
  • October 22, 2020

Update to this question: This does appear to be a bug, and as a result I have filed FMEENGINE-67411 to track this issue. I'll post an update here once this has been addressed!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings