Closed ihormartsekha-okta closed 5 years ago
@ihormartsekha-okta The sample look good. My observation is that the fingerprint sensor and callback is always on and listening. I observed that when trying to sign out it would not work after 10 seconds. But after simulate the fingerprint sensor in the emulator I can sign out without the dialog.
Can we make the sample that only initialize and use the fingerprint sensor to authenticate only when it is needed? For example when trying to decrypt data, you should catch a UserNotAuthenticatedException
then initialize the fingerprint sensor instead of always listening?
Some issues I see:
Resume app always ask for smart lock:
no
for using smart lock after authentication Whats the difference between SIGN IN
and FINGERPRINT SIGN IN
? Both looks like are doing the same flow that asks if the user want to enable smart lock after auth completes.
Sign out button doesn't work after 10 seconds. After authentication sign out doesn't do anything after waiting for 10s or more. But sign out works for the first 10s after any operation that requires finger print such as refresh token. Or if you touch the fingerprint sensor to authenticate even without a prompt to do so. This is probably due to the validity period. But this should not happen since the the TokenResponse and all the needed data for sign out should be in cache.
When refreshing a token a toast shows the following error:
Note the above toast error and dialog does not show up when I touch the fingerprint sensor first. Is the toast just for debugging?
After relaunching the app and canceling the smart lock dialog trying to sign in again will show the following screen with the shown toast:
Sometimes when exiting the app and returning. It gets stuck in the following screen:
Mode to new oidc library Added sample of Rx implementation