How to: 4.2 security and OOB

[Jari]

We are building a system consisting of two devices (nRF52832) that need to communicate in a secure manner. We want to use the secure connection offered by BT4.2 and we want to use NFC to do OOB bonding as we have no UI. We plan to use the Adafruit PN532 NFC Shield on one device and the build in NFC tag on the other. I guess we should use the Peer Manager to handle the security aspects? I have tried to apply the security on the blinky sample projects using the Peer Manager. This however fails and I am unsure how to use the Peer Manager with OOB. I would like to get OOB working regardless of NFC. Does anybody have experience with OOB and the Peer Manager?

[Petter Myhre]

You can use the Peer Manager to handle bonding. What is failing? What have you done? Have you tried to follow this tutorial?

[Jari]

I have been looking at the “migrate from Device Manager to Peer Manager”. I am net to Nordic devices and I know nothing about the Device manager. I need to generate the OOB data on the peripheral device. I guess the NFC examples pretty much covers that.

I need to handover this OOB data to the Peer Manager on the central device – how do I do that on s132?

I need to setup the Security parameters (pm_sec_params_set): I guess that oob should be set on the Central device as it is supposed to receive OOB date and that oob is NOT set on the Peripheral device as it will not receive any OOB data.

[Petter Myhre]

OOB should be set on both sides. Like under OOB bonding here.

When you bond you will get the BLE_GAP_EVT_AUTH_KEY_REQUEST event on both sides, and you include the OOB key with sd_ble_gap_auth_key_reply() on both sides.

Please check this and this.