1 - FIDO Reference ASM is a newly implemented ASM capable of supporting multiple FIDO spec compliant Authenticators.
2 - Target platform version is Tizen 3.x.
4 - It generates the following:
8 4. Multiple Authenticator plugin rpms (To be added)
11 1. rpm -ivh --force --nodeps <fido-asm rpm>
12 2. rpm -ivh --force --nodeps <fido-asm devel rpm> [Only for internal unit level testing]
14 4. rpm -ivh --force --nodeps <asmui rpm>
15 5. If you are using July Binary then
16 chsmack -e System::Privileged /usr/bin/tpk-backend
17 6. tpk-backend -y org.tizen.asmui --preload
19 - Instllation: Roaming Authenticator
20 1. Pre-condition: Two TM1 devices must be connected to same Multicast AP.
21 2. Let TM1S = Server Device (Mobile), TM1C = Client Device (TV)
23 a. Install fido-asm, fido-asm-ui and fido-pin-auth
26 a. Install fido-client, fido-asm and FIDOSample
28 5. After reboot, give some time to both devices to connect to the AP.
29 6. On Client Device, open FIDOSample app and test:
35 1. FIDOSample can be used to test, however the json must have AAID matched with one of the installed Authenticator's.
36 2. fido-devel rpm can be used for all unit level testing (except UI), after installation,
37 run /opt/usr/devel/fido_asm/tc/fido-asm-shell-tc and select unit testing options.
38 3. For UI testing, first enable ASM_UI_TEST in server/ClientListener.cpp, then build fido-asm, reboot.
39 - Then, for Transaction UI testing, run from device shell,-
41 --dest=org.tizen.fidoasm \
45 org.tizen.fidoasm.asm_request \
47 - For Account UI testing, run from device shell,-
49 --dest=org.tizen.fidoasm \
53 org.tizen.fidoasm.asm_request \
55 - Mobile Emulator default theme might create visibility issue for UI, use General Purpose emulator.(To be fixed later)