Skip to content
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.

Consolidated Logic to Determine Device Security Stance #70

Closed
linuxwolf opened this issue Aug 28, 2018 · 4 comments
Closed

Consolidated Logic to Determine Device Security Stance #70

linuxwolf opened this issue Aug 28, 2018 · 4 comments
Labels
feature-unlocking task Issue describes a task that needs to be completed but is not a defect or enhancement in itself.

Comments

@linuxwolf
Copy link
Contributor

Use the KeyguardManager to determine if the user's device is secured using a Pattern/PIN/Password, and the FingerprintManager to determine if fingerprint hardware is available and at least one fingerprint is enrolled.

This detection happens during:

  • Onboarding to help configure a higher security stance within the app
  • Settings to determine what configuration options are available
@linuxwolf linuxwolf added task Issue describes a task that needs to be completed but is not a defect or enhancement in itself. feature-unlocking labels Aug 28, 2018
@linuxwolf linuxwolf mentioned this issue Oct 19, 2018
Closed
@devinreams
Copy link
Contributor

Some of this is happening in #68 and #64 (in that order)

May be close-able once those are landed

@devinreams devinreams changed the title Determine Device Security Stance Logic to Determine Device Security Stance Oct 25, 2018
@sandysage sandysage mentioned this issue Oct 25, 2018
Closed
@sashei sashei mentioned this issue Oct 25, 2018
Merged
5 tasks
@devinreams devinreams changed the title Logic to Determine Device Security Stance Consolidated Logic to Determine Device Security Stance Oct 25, 2018
@devinreams devinreams added this to the M6 - Onboarding + Polish milestone Oct 25, 2018
@devinreams devinreams removed this from the M6 - Internal Alpha milestone Nov 14, 2018
@sandysage
Copy link

@linuxwolf would you mind taking a look to see if we're good to close this issue or if we need to do something else here?

@sashei
Copy link
Contributor

sashei commented Jan 17, 2019

@linuxwolf ping :)

@sashei
Copy link
Contributor

sashei commented May 15, 2019

Let's call this resolved unless we need any further documentation.

@sashei sashei closed this as completed May 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
feature-unlocking task Issue describes a task that needs to be completed but is not a defect or enhancement in itself.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@devinreams @linuxwolf @sandysage @sashei