optum / openid-client-server Goto Github PK

I work within EFWAE in Optum and was having an issue with the openid-client-server and was referred here by Alex Aavang.

While investigating why our react front end was seeing calls that should be JSON as XML I came across a possible bug within the server. The headers from node-fetch are key value pairs where the value is an array with a single value. The node response header method, res.writeHead expects these headers to be set as strings rather than arrays. This is not the case when performing a getUserInfo request to the OAuth provider but only happens with the response from our koa api.

Adding the following code at the beginning of the sendResponse method in /middleware/util.ts resolves the issue as it converts the arrays into strings. Without these changes none of the headers seen in the response from the koa API are forwarded to the client.

if(headers.raw){ headers = JSON.parse(JSON.stringify(headers.raw())) }

This can also been seen in the network tab of the page using the server. As you can see the response does not have a content-type and is therefore seen as xml.