Financial Address Mapper - Issues, Questions & Clarifications

[lalithkota]

I have a couple of questions regarding Sunbird-RC's Financial Address Mapper, which is available here.

• We have installed all the components described in the docker compose, and explored the available UI and Mapper APIs. We are able to call the link API and see the data being linked in the DB.
• We are unable to call the resolve API to get the resolution or the financial address. The yes_no response also doesn't seem to work. We are always getting a static account provider info output (because of this(?))
• When using the asynchronous APIs described, the response always seems to be routed to a preconfigured callback service (because of this (?)). It doesn't seem to be using the sender-uri/sender-id/receiver-id/url from the header (described in the G2P-Connect spec here for example).
  • How do we give a different callback URL per each API call?
• The Signature value in the request (for any API call) seems to be ignored. The request seems to pass through, for any given value in the signature. Is this the desired output?
• Also as part of the latest draft of 1.0.0 of the Mapper API Spec, synchronous APIs are also added. For example here. Are there any plans for Sunbird's impl to support this synchronous APIs?

How we can proceed with the above?

Thanks

[holashchand]

Hi @lalithkota

1. Static account info is mocked.
2. The mapper service is created to use one provided service only. You will require to modify code to use different callback for given api.
3. The validation for signature is not done in this demo.

You can refer to this PR #665 to know more about the functionalities implemented