+ +

FIDO Client Sample Overview

+ +

The Fido-client sample application demonstrates how to use fido authentication.

The following figure illustrates the main view of the Fido-client application in its normal state.

This sample application is done using predefined uaf protocol messages. If you want to test with actual FIDO server then you need to replace the json values with server specific parameters.

+ +

Figure: Fido-client main view

Fido-client main view

+ +

Prerequisites

FIDO-UAF should be supported by the device.

+ +

Implementation

+ +

We have used hard-coded json value for registeration, authentication and derigsteration. The json files are stored in ../Fido_sample/res.

In this sample application, information(use) for fido uaf application api's have been provided. For more information, click here.

+ +

Find Authenticator

+ +

Find Authenticator function is used to obtain the list of all available authenticators.

+ +

Figure: Find Authenticator

Find Authenticator

+ +

After you click Find Authenticator on the main screen, the discover response will be displayed as a pop up (as shown in the above figure).

+ +

+void
+start_discover(void *data, Evas_Object *obj, void *event_info)
+{
+   int ret = fido_foreach_authenticator(auth_list_cb, data);
+
+   if (ret != FIDO_ERROR_NONE)
+      __show_error(ret, (appdata_s *)data);
+}
+

+ + +

Check UAF Message Supported

+ +

This function checks whether the given UAF protocol message can be processed by the device.

+ +

Figure: Check UAF Message Supported

+ +

Check UAF Message Supported

+ +

After you click Check UAF Message Supported on the main screen, on success 'TRUE' will be displayed in a pop up (as shown in the above figure).

+ +

+void
+start_check_policy(void *data, Evas_Object *obj, void *event_info)
+{
+   int ret = fido_request_is_supported(json_reg, _policy_cb, data);
+}
+

+ +

Protocol Conversation

+ +

The core UAF protocol consists of conceptual conversations between a FIDO UAF Client and FIDO Server.

+ +

Registeration.

UAF allows the relying party to register a FIDO Authenticator with the user's account at the relying party. The relying party can specify a policy for supporting various FIDO Authenticator types. A FIDO UAF Client will only register existing authenticators in accordance with that policy.

Figure: Registeration

Registeration

After you click Registeration on the main screen, the registeration response message is visible on the home screen as a pop-up (as shown in the above figure).

+void
+start_registration(void *data, Evas_Object *obj, void *event_info)
+{
+   if (json_reg != NULL) {
+      int ret = fido_request_get_registration_response(json_reg, NULL, _process_cb, data);
+
+      char str[2048] = {0,};
+      str[0] = '\0';
+      strcpy(str, "REGISTRATION RESPONSE | ");
+      char tmp[1024] = {0,};
+      sprintf(tmp, "ret = [%d] | ", ret);
+      strcat(str, tmp);
+   }
+}
+

Authentication.

UAF allows the relying party to prompt the end user to authenticate using a previously registered FIDO Authenticator. This authentication can be invoked any time, at the relying party's discretion.

Figure: Authentication

Authentication

After you click Authentication on the main screen, authentication response message is visible on the home screen as a pop-up (as shown in the above figure).

+void
+start_auth(void *data, Evas_Object *obj, void *event_info)
+{
+   if (json_auth != NULL) {
+      int ret = fido_request_get_authentication_response(json_auth, NULL, _process_cb, data);
+
+      char str[2048] = {0,};
+      str[0] = '\0';
+      strcpy(str, "AUTHENTICATION RESPONSE | ");
+      char tmp[1024] = {0,};
+      sprintf(tmp, "ret = [%d] | ", ret);
+      strcat(str, tmp);
+   }
+}
+

Deregistration.

The relying party can trigger the deletion of the account-related authentication key material.

Figure: Deregistration

Deregistration

After you click Deregistration on the main screen, on successful operation 'SUCCESS' message response is visible on the home screen as a pop-up (as shownin the above figure).

+void
+start_de_registration(void *data, Evas_Object *obj, void *event_info)
+{
+   if (json_reg != NULL) {
+      int ret = fido_request_get_deregistration_response(json_dereg, NULL, _process_dereg_cb, data);
+
+      char str[2048] = {0,};
+      str[0] = '\0';
+      strcpy(str, "DE-REGISTRATION RESPONSE | ");
+      char tmp[1024] = {0,};
+      sprintf(tmp, "ret = [%d] | ", ret);
+      strcat(str, tmp);
+   }
+}
+

+ +

Set Server Result

+ +

Set Server Result is used to indicate the status code resulting from a FIDO UAF message delivered to the remote server.

Set Server Result with Success
Set Server Result with Failure

Figure: Set Server Result

Set Server Result

After you click Set Server Result on the main screen, on successful operation 'SUCCESS' message response is visible on the home screen as a pop-up (as shown in the above figure).

+ +

Set Server Result with Success

+void
+start_notify_pos(void *data, Evas_Object *obj, void *event_info)
+{
+   if (json_reg != NULL)
+      int ret = fido_uaf_get_response_message(json_reg, NULL, _process_cb_for_notify_pos, data);
+}
+
+static void
+_process_cb_for_notify_pos(fido_error_e tizen_error_code, const char *uaf_response, void *user_data)
+{
+   if (tizen_error_code == 0) {
+      int ret = fido_uaf_set_server_result(FIDO_SERVER_STATUS_CODE_OK, uaf_response);
+
+      char *error_string = get_error_code(tizen_error_code);
+      create_popup(error_string, (appdata_s *) user_data);
+      free(error_string);
+   }
+   else {
+      __show_error(tizen_error_code, (appdata_s *)user_data);
+   }
+}
+
+static void
+__show_error(int tizen_error_code, appdata_s *app_data)
+{
+   char *error_string = get_error_code(tizen_error_code);
+   create_popup(error_string, app_data);
+   free(error_string);
+}
+

Set Server Result with Failure

+void
+start_notify_neg(void *data, Evas_Object *obj, void *event_info)
+{
+   if (json_reg != NULL)
+      int ret = fido_uaf_get_response_message(json_reg, NULL, _process_cb_for_notify_neg, data);
+}
+
+static void
+_process_cb_for_notify_neg(fido_error_e tizen_error_code, const char *uaf_response, void *user_data)
+{
+   if (tizen_error_code == 0) {
+      int ret = fido_uaf_set_server_result(0, uaf_response);
+
+      char *error_string = get_error_code(tizen_error_code);
+      create_popup(error_string, (appdata_s *) user_data);
+      free(error_string);
+   }
+   else {
+      __show_error(tizen_error_code, (appdata_s *)user_data);
+   }
+}
+

+ + + +