Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Security/Privacy: Uphold sandbox for KYC is prevented from accessing Camera #1807

Closed
mandar-brave opened this issue Oct 23, 2018 · 1 comment
Closed

Security/Privacy: Uphold sandbox for KYC is prevented from accessing Camera #1807

mandar-brave opened this issue Oct 23, 2018 · 1 comment
Labels
closed/duplicate Issue has already been reported closed/invalid

Comments

@mandar-brave
Copy link

See parent issue for feature description #923

Issue: When we launch the sandbox from Brave Rewards panel for add-funds. During the add-funds work flow (See primary issue for docs), the Uphold sandbox triggers a Jumio API that is getting access to camera automatically blocked for documentation check.

What is expected: User should be prompted to be able to access camera.

How to test: Disable Shields and go through the test link to get camera access

Test Link (to reproduce issue): https://uphold-widget-uhocggaamg.now.sh/

Issue has been discussed with Tom in detail and preliminary call with Uphold has concluded.

Please assign to @tomlowenthal
This is scheduled for 0.56 milestone
@rebron rebron added this to the 0.56.x - Beta milestone Oct 25, 2018
@bsclifton bsclifton modified the milestones: 0.56.x - Beta, 0.57.x - Dev Oct 26, 2018
@mandar-brave mandar-brave mentioned this issue Oct 26, 2018
Closed
@mandar-brave
Copy link
Author

Closing per chat with @tomlowenthal .
Issue recorded in #923

@rebron rebron modified the milestones: 0.57.x - Dev, Dupe / Invalid / Not actionable Oct 30, 2018
@kjozwiak kjozwiak added closed/duplicate Issue has already been reported and removed feature/rewards labels Nov 6, 2018
@bbondy bbondy removed this from the Dupe / Invalid / Not actionable milestone May 30, 2020
This was referenced Dec 9, 2020
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
@btlechowski btlechowski mentioned this issue Jan 5, 2021
Closed
@privacy313 privacy313 mentioned this issue Jan 5, 2021
Open
This was referenced Jan 6, 2021
Closed
Closed
Closed
Closed
@julesrx julesrx mentioned this issue Jan 6, 2021
Open
This was referenced Jan 6, 2021
Open
Closed
@justinmcgrath justinmcgrath mentioned this issue Jan 6, 2021
Open
@sahilc0 sahilc0 mentioned this issue Jan 7, 2021
Closed
@SungHwan-J SungHwan-J mentioned this issue Jan 7, 2021
Closed
@jorgicio jorgicio mentioned this issue Jan 7, 2021
Open
This was referenced Jan 7, 2021
Closed
Closed
@srirambv srirambv mentioned this issue Jan 8, 2021
Open
This was referenced Jan 8, 2021
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
@eljuno eljuno mentioned this issue Jan 10, 2021
Open
@rebron rebron mentioned this issue Jan 11, 2021
Closed
@nerdyman nerdyman mentioned this issue Jan 15, 2021
Closed
@btlechowski btlechowski mentioned this issue Jan 18, 2021
Closed
@JackKenney JackKenney mentioned this issue Jan 24, 2021
Open
@btlechowski btlechowski mentioned this issue Mar 8, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed/duplicate Issue has already been reported closed/invalid
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@tildelowengrimm @bbondy @kjozwiak @bsclifton @rebron @mandar-brave