How can I enforce OOB Rx in some peripherals but not in others?

[David Fernandez]

Hi there,

To do LESC with some peripherals supporting OOB Rx, and some not, and the central supporting OOB Tx, I was wondering how to correctly enforce the OOB for the right peripherals.

I have been locking at the charts in the documentation, but they don't seem to account for the peer manager...

Seems that it starts, after echanging the OOB data, with sd_ble_aunthenticate... I wonder where should I hook that call if using the peer manager, as after connection, I usually call pm_conn_secure..., and if it will request oob authentication or not depending on the parameters passed. there and to SEC_PARAMS_REQUEST event.

Regards

[Bjørn Kvaale]

Looking at the ble_app_hrs central example, it seems that the pm_sec_params_set() function can be called multiple times (see link). Once the central identifies whether the peripheral you want to connect to supports LESC OOB, you may be able to change the pm_sec_params_set() to reflect this change.