tink-crypto / tink-crypto/tink-java

Android User Authentication

Open
#12 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

p3
Dominant language
Java
Stars
305
Forks
42
PR merge metrics
No merged PRs in 30d

Description

Your docs state

Android Keystore is only useful when you want to require user authentication for key use

but your implementation looks like it would need a complete rewrite of the AndroidKeystoreKmsClient.java to be able to handle user authentication for key use.

Is that intended? Or is there an easy way around the limitations of the existing implementation?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the Android Keystore authentication statement in the documentation with AndroidKeystoreKmsClient.java. Determine whether user authentication for key use is supported by the current implementation or requires broader changes; done means the intended behavior and required scope are clearly established.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
authentication, mobile-dev, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.