No BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST with secure connection?

[Marcel Mulder]

When I add an attribute with BLE_GAP_CONN_SEC_MODE_SET_OPEN I get a BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST event when I try to read it. I do not however get a BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST event when I add the attributes with BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM. Why?

[Ulrich Myhre]

You should not get an authorize request unless you specifically set the rd_auth or wr_auth flags in the characteristic metadata.

I suspect you are not memsetting your variables to zero, and that those bits take on random values depending on where the compiler decides to place the data.

[Marcel Mulder]

everythings is ok, memset and rd_auth flag. The onlything I change is the access level using the macro's as described above.

[Marcel Mulder]

To make it more clear. It works! But not if I use BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM or BLE_GAP_CONN_SEC_MODE_SET_ENC_WITH_MITM for that matter.

[Ulrich Myhre]

Okay, sorry I misunderstood you. If you set that you need encryption to read/write to an attribute, the stack will automatically respond with "insufficient authentication" when the value is accessed in that restricted way. If you encrypt the link, the you should get authorize requests again.

[Marcel Mulder]

Ah, ok, normally (with the phone) I have an encrypted connection but for testing I use a tool which connects without encryption. I wanted to test the status I return, but it seems the softdevice already handles this than. I don't know if that's wanted behavior. If a set rd_auth than I aspect the authorize requests. Not that if this than that or else if this than etc... I bump into more places where the softdevice handles stuff but where I aspect the application should handle it. I have used other solutions that are more transparent. Or the firmware/softdevice handles it or the application. Without conditions.

Anyway it clear now. Thanks.