-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android - We are able to activate received VCs #512
Comments
As discussed, you have raised another bug for which we will not provide binding option . Hence this is not a valid bug, |
We will be creating a separate Verifier app. Hence any verifier-related bugs/issues will not be considered a priority for Beta release. Will be picked up only after addressing all blockers and critical bugs if capacity is available with the team. CC @Sujithbn @MonobikashDas @Raginikrishnamurthy @Anushree09-N @santhoshsunder @ravikp |
… received id's tab
refactor(mosip#512): [Vijay|Bhargavi] remove activation button for vc on received Id's tab
Issue merged in the PR - #595 |
The following PRs implements restrictions for verifier to not activate the received VC and do any actions on it. The PRs have been merged in 28-02-2023 Release and the latest commit id on mosip/inji/develop is 7cdee82 |
Verified this issue in qa-1201-b2 environment, now removed Activation status info of VC on the receiver side, so we can not bind received VCs and should not be able to login with it. I am attaching the video and the device details below for reference. Hence closing the bug. Untitled.1.mp4Tested in: - |
Describe the bug
We are able to activate received VCs and login through IDP with received VCs
To Reproduce
Prerequiste: download a VC and dont bind, receive a VC
Expected behavior
We should not able to bind received VCs and should not able to login with it
Observed
we are able to bind received VCs and able to login with it
Video
https://user-images.githubusercontent.com/102220709/215513078-120ff9c3-a011-4c4d-8f39-b4a061d6df53.mp4
Smartphone :
The text was updated successfully, but these errors were encountered: