[Openid-specs-fapi] Issue #47: Confusing use of `client` and `server` (openid/fapi)

Dave Tonge issues-reply at bitbucket.org
Wed Dec 7 13:28:39 UTC 2016


New issue 47: Confusing use of `client` and `server`
https://bitbucket.org/openid/fapi/issues/47/confusing-use-of-client-and-server

Dave Tonge:

https://bitbucket.org/openid/fapi/annotate/d4edc14c0b76155c97623edb521bfdc56afd64b7/Financial_API_WD_001.md?at=master&fileviewer=file-view-default#Financial_API_WD_001.md-252

*shall send the `x-fapi-InteractionId` with the value set to the one received from the **client** in the `x-fapi-InteractionId` request header or a [RFC4122] UUID value created by the **server** if there was no corresponding request header to track the interaction, e.g., `x-fapi-InteractionId: c770aef3-6784-41f7-8e0e-ff5f97bddb3a`; and*

I suggest that this sentence is reworded to make it clear which client and server are being referred to.






More information about the Openid-specs-fapi mailing list