Send an insufficient authentication request

[brianreinhold]

How can I, from the pc-ble-driver API, send an insufficient authentication request without configuring a characteristic to be secured?

I am testing out new standards. One of the biggest user nightmares in Bluetooth is pairing - whether or not the device even pairs. Patients of health devices do not understand this concept. So the idea is that the collector queries the peripheral if it supports pairing and if it does, the collector begins pairing. This would be part of the health device communication profile protocol. If the collector does not do this query or does it and does not pair, I want to respond to any collector request with 'insufficient authentication'.

I do not see anyway to send this error in response to a write on an (unsecured) control point. I do not want to place security on the control point as that is the first command the collector will send (do you support pairing?).

Something like this would save a great deal of user headache.

Thanks.

[Kenneth]

Hi,

Not sure if I understand here, typically you can find that when you connect to an iPhone, Android or PC that the user is prompted to pair with the device. This UI seem to be pretty straight forward enough, even though the different OS's are actually doing this differently (the trigger to execute bonding is different) on the lower level of the link. E.g. Windows will send a security request when link is established to query the security supported, while iOS does a GATT database discovery to find if any of the services and characteristics require security (insufficient authentication). The peripheral examples that supports pairing (aka bonding) works independent of which method is used, the central may do this as it see fit.

Best regards,
Kenneth