Code differences between opencrvs-core and mosip-mediator #6395
Replies: 2 comments
-
Hi @NagarjunaKuchi as you pointed out the mosip mediator is a bit behind from the recent changes we made to core. But rest assured as it is in our roadmap towards 1.4.0 to bring it up to date. Although I can see that you already have a rough idea of what might need to be changed, basically the data in the body of request will now need to be provided in the request uri instead. So if you have perhaps already made those changes or you want to do it then a PR would be highly appreciated 😄 . |
Beta Was this translation helpful? Give feedback.
-
Hi @NagarjunaKuchi I just wanted to also point out that we are working with MOSIP to make some changes to mosip-mediator. It is currently coded to be hosted within the MOSIP stack and we are moving it out to be hosted on the OpenCRVS stack instead. You can expect to see some gradual movement in this repo in the coming weeks. I will let you know when it is ready for testing again. As @Zangetsu101 pointed out we will bring it up to date. FYI our release calendar changed this week. We are poised to release 1.4 with some other infrastructure changes and this mosip-mediator upgrade will now be in 1.5. The schedule for 1.5 is currently to be released in beta at the end of March this year I'm afraid. |
Beta Was this translation helpful? Give feedback.
-
Hi Team,
We are trying to integrate opencrvs with MOSIP. After subscribing the events, data is not flowing to MOSIP through mosip-mediator. When we analyze the code, found some differences in the code.
opencrvs-core has some changes to support OAuth 2.0 . These changes were not reflecting in mosip-mediator.
We are using master branch of mosip-mediator and opencrvs-core.
Code -Differences :
mosip-mediator
opencrvs-core
OAuth 2.0 changes
Please let us know is there any other branch available which is compatible with mosip-mediator.
Beta Was this translation helpful? Give feedback.
All reactions