I am trying to test the deactivation of uin. When trying to deactivate using the idrepo update api, it is working fine and deactivation is success and even notified to IDA.
But not working with a deactivation packet. In the UIN generator stage, we are passing the status as DEACTIVATED also to the update draft api, but it seems the idrepo update draft api is not using this status field itself. So even after the packet is processed, the uin is not deactivated.
Hello @manish_choudhary
Thank you for reaching out to us. Kindly allow us some time, and we will revert with the details at the earliest.
Regards
Likhitha R L
On behalf of MOSIP team
Dear @manish_choudhary,
As per MOSIP’s design policy, deactivation of the UIN is not recommended; therefore, this flow is not currently supported.
If you have a specific use case that requires UIN deactivation, please do share more details. We would be happy to understand your requirement and guide you accordingly.
Regards,
Varaniya S
On Behalf of Team MOSIP
Thanks @Varaniya1 for the clarification.
I am trying to integrate opencrvs system with the MOSIP system. So in opencrvs when we register a death event, we need to deactivate the deceased’s UIN in the MOSIP. Please guide on how we can do this, if UIN deactivation is not recommended.
In terms of crvs integration and death flow, we are updating the death flag to inform relying party that the provided UIN belong to a person who have passed away. so this also follows an update flow while UIN will be in active status.
Please refer to this documentation to understand the rationals behind this design:
Please refer to this link to know the workflow and how you can proceed to integrate the same:
Regards,
Varaniya S
On Behalf of Team MOSIP
Thanks @Varaniya1 , this is really helpful.
Is this design completely implemented in MOSIP?
For the flag ‘declaredAsDeceased‘, we need to add in idschema, identity mapping and auth policy. These are configuration changes but code wise I am not able to see any changes in the reg proc or id repo for this. For instance in the uin generator stage there is no separate condition to handle death flow(crvs_death registration type).
Please let me know if I am missing anything here.
Hi @manish_choudhary ,
Code level implementation is completed as part of the release “Registration v1.2.1.1” and the code changes are available currently in all upper versions as well. (attached the release note for the reference)
Although as process we define the flow specifically as crvs_death but MOSIP treat this as update flow only.
Please proceed with this approach and if you are facing any issue do let us know, we will help you to resolve on the same
Regards,
Varaniya S
Team MOSIP
Ok @Varaniya1 thanks.
So we are making the declaredAsDeceased flag as true or Y, and same will be issued to IDA. Now, if some relying party do authentication, it will be success but in the kyc response we will send this flag also, based on this the relying party can decide. is my understanding correct?
And that means the normal auth without kyc(for example demo auth with IDA in opencrvs) will be a success, so how will the party knows this is Deceased.
yes your understanding is correct. for Yes/no authentication also we will send this flag so the relying party will be aware on the same
for Yes/no authentication also we will send this flag so the relying party will be aware on the same
Can you elaborate a little on this, how we are sending this flag in the response in this case. As we only send authStatus and authToken in the response.
Hi @Varaniya1 ,
Can you please clarify the last query(how we are sending the flag in the response in Yes/no authentication?). If the implementation is already present then how it is working, if not do we need to customize accordingly?