mirror of
https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC.git
synced 2024-11-22 22:00:59 +02:00
Created Use Cases (markdown)
parent
43d94dff16
commit
6cca0a430b
58
Use-Cases.md
Normal file
58
Use-Cases.md
Normal file
@ -0,0 +1,58 @@
|
|||||||
|
**Use Case #1**
|
||||||
|
|
||||||
|
**Use Case Title:**
|
||||||
|
User authentication for the test website.
|
||||||
|
**Preconditions:**
|
||||||
|
The user has the authentication mobile application installed on his/her smartphone.
|
||||||
|
The user’s phone supports NFC technology.
|
||||||
|
The user has given the application permissions that it requires, so that the application can use NFC technology and communicate with the web service.
|
||||||
|
The user has an ID-card with NFC interface.
|
||||||
|
**Primary actor:**
|
||||||
|
User
|
||||||
|
**Main success scenario:**
|
||||||
|
1. The user starts a login process on the website and selects the mobile authentication application option.
|
||||||
|
2. The website launches the authentication application on the user’s smartphone.
|
||||||
|
3. The user places the ID-card against the mobile phone (near the NFC chip of the mobile). (Use Case #2)
|
||||||
|
4. The application asks the user to enter a valid PIN.
|
||||||
|
5. The application generates a web-eID compatible JWT.
|
||||||
|
6. The token is delivered to the website that started the authentication process.
|
||||||
|
7. The user is logged into the website.
|
||||||
|
|
||||||
|
**Extensions:**
|
||||||
|
1. The authentication application is not found.
|
||||||
|
a. The website informs the user that the login process failed.
|
||||||
|
3. The connection between ID-card and smartphone is not established.
|
||||||
|
a. The application cancels the authentication process.
|
||||||
|
b. The user is directed back to the website.
|
||||||
|
4. The user enters an invalid PIN.
|
||||||
|
a. Max retries are not exceeded - The user is asked to enter the PIN again.
|
||||||
|
b. Max retries are exceeded - ID-card authentication feature will be disabled. Application notifies the user.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Use Case #2**
|
||||||
|
|
||||||
|
**Use Case Title:**
|
||||||
|
Detecting a nearby ID-card.
|
||||||
|
**Preconditions:**
|
||||||
|
The mobile authentication app is active.
|
||||||
|
The user has an ID-card with NFC interface.
|
||||||
|
The ID-card is currently not in the range of the mobile NFC chip.
|
||||||
|
**Primary actor:**
|
||||||
|
User
|
||||||
|
**Main success scenario:**
|
||||||
|
1. The authentication app notifies the user that the ID-card is currently not being detected.
|
||||||
|
2. The user puts the ID-card against the NFC chip of the smartphone.
|
||||||
|
3. The app notifies the user that the ID-card has been detected.
|
||||||
|
|
||||||
|
**Extensions:**
|
||||||
|
2a. The user fails to put the ID-card against the NFC chip.
|
||||||
|
a. The app keeps waiting for the user (timeout will be decided in the future).
|
||||||
|
b. The user puts the ID-card against the NFC chip.
|
||||||
|
c. The authentication process continues.
|
||||||
|
2b. The user closes the app.
|
||||||
|
a. The authentication process is cancelled.
|
||||||
|
3. The user uses an invalid or expired ID-card
|
||||||
|
a. The app notifies the user that the ID-card is not valid.
|
||||||
|
b. The app keeps waiting for the user.
|
Loading…
Reference in New Issue
Block a user