Authenticated pairing callback structure. More...

#include <conn.h>

Data Fields
enum bt_security_err(*	pairing_accept )(struct bt_conn conn, const struct bt_conn_pairing_feat const feat)
	Query to proceed incoming pairing or not.
void(*	passkey_display )(struct bt_conn *conn, unsigned int passkey)
	Display a passkey to the user.
void(*	passkey_display_keypress )(struct bt_conn *conn, enum bt_conn_auth_keypress type)
	Receive Passkey Keypress Notification during pairing.
void(*	passkey_entry )(struct bt_conn *conn)
	Request the user to enter a passkey.
void(*	passkey_confirm )(struct bt_conn *conn, unsigned int passkey)
	Request the user to confirm a passkey.
void(*	oob_data_request )(struct bt_conn conn, struct bt_conn_oob_info info)
	Request the user to provide Out of Band (OOB) data.
void(*	cancel )(struct bt_conn *conn)
	Cancel the ongoing user request.
void(*	pairing_confirm )(struct bt_conn *conn)
	Request confirmation for an incoming pairing.
void(*	pincode_entry )(struct bt_conn *conn, bool highsec)
	Request the user to enter a passkey.
uint32_t(*	app_passkey )(struct bt_conn *conn)
	Allow the application to provide a passkey for pairing.

Detailed Description

Authenticated pairing callback structure.

Note: The callbacks are invoked from a thread context, never from an ISR. Whether a callback is invoked from a context internal to the stack or synchronously from within the API call that triggers it, and from which context, is not part of the API and may change between releases. See @rstref{Callback execution contexts <bluetooth_callback_contexts>} for the hazards of blocking in a callback and their mitigations.

The documentation for this struct was generated from the following file:

Data Fields