INSUFFICIENT_AUTHENTICATION with Master Control Panel on PC with Dongle

RE: INSUFFICIENT_AUTHENTICATION with Master Control Panel on PC with Dongle

sbailes — Fri, 17 Jun 2016 14:33:24 GMT

What if I don't have a characteristic that supports the read and write permissions? My application uses DFU and NUS services and that's it.

RE: INSUFFICIENT_AUTHENTICATION with Master Control Panel on PC with Dongle

run_ar — Fri, 17 Jun 2016 07:27:27 GMT

No, this is when you initialize characteristics. See the tutorial on how to add those here.

RE: INSUFFICIENT_AUTHENTICATION with Master Control Panel on PC with Dongle

sbailes — Thu, 16 Jun 2016 15:21:16 GMT

Where would that go? (The read and write_perms) Would it go in gap_params_init? When I try putting it there it stops advertising.

RE: INSUFFICIENT_AUTHENTICATION with Master Control Panel on PC with Dongle

run_ar — Thu, 04 Feb 2016 13:15:37 GMT

If you look at the service initializing procedure you can see that we set cccd and attr properties like this: BLE_GAP_CONN_SEC_MODE_SET_OPEN(&attr_md.read_perm); //for read permissions BLE_GAP_CONN_SEC_MODE_SET_OPEN(&attr_md.write_perm); // for write permissions

The example above is open but you can also require bonding with or without MITM using these: BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM
BLE_GAP_CONN_SEC_MODE_SET_ENC_WITH_MITM

If it says WITH_MITM your device has to support bonding with MITM (passkey) for you to be able to write to this characteristic.

RE: INSUFFICIENT_AUTHENTICATION with Master Control Panel on PC with Dongle

medamarko — Thu, 04 Feb 2016 13:04:28 GMT

Thanks on response, already tried with clearing bonding list from both sides. Sorry if this is stupid question but how i can make sure that security requirements are matching bonding capabilities? Is there any way i can read it out or check with some tool?

RE: INSUFFICIENT_AUTHENTICATION with Master Control Panel on PC with Dongle

run_ar — Thu, 04 Feb 2016 11:24:18 GMT

Try to delete all bonds before you connect to the device, then bond again. Bonding is needed if you get the insufficient authentication error. If the bond information is lost on one side, you will also have to delete this on the peer before you bond again. You also have to make sure the security requirements for your characteristics matches the bonding capabilities of your device.