Topics

Documentation on bt_conn_auth_cb(...)


Theis Orthmann Blickfeldt Jørgensen (TTJO)
 

Hi,

 

I am trying to understand the GAP API for Zephyr Bluetooth Stack, and came across bt_conn_auth_cb(…). This callback function seems to be completely undocumented.
Anyone who know what the callback-criteria is for the registered functions?

 

If the responsible developers at Intel reads this message, it would be nice with some explanatory comments in the source code.

 

Venlig hilsen/kind regards

Theis Orthmann Blickfeldt Jørgensen

Embedded Software Developer, M.Sc.EE.

 

Oticon A/S

Kongebakken 9

DK-2765 Smørum

 

ttjo@...

www.oticon.com

 


Johan Hedberg
 

Hi Theis,

On Thu, Jun 14, 2018, Theis Orthmann Blickfeldt Jørgensen (TTJO) wrote:
I am trying to understand the GAP API for Zephyr Bluetooth Stack, and
came across bt_conn_auth_cb(...). This callback function seems to be
completely undocumented.
Anyone who know what the callback-criteria is for the registered
functions?
They map directly to the authentication methods from the Security
Manager protocol.

If the responsible developers at Intel reads this message, it would be
nice with some explanatory comments in the source code.
The lack of documentation for these is indeed an oversight. Could you
open a github issue so we can track getting the documentation
implemented? Btw, the response functions to the callbacks (the ones that
solicit a response anyway) are at least documented, and describe which
callback from bt_conn_auth_cb they relate to (I'm referring here to the
likes of bt_conn_auth_passkey_entry, bt_conn_auth_passkey_confirm, etc).

Johan


Theis Orthmann Blickfeldt Jørgensen (TTJO)
 

Thank you,

however it is not ideal that one should read/understand the SMP to understand when a given CB is expected to occour.

I have submitted the issue on GitHub.

\Theis