:orphan:

.. title:: BT_SMP_APP_PAIRING_ACCEPT

.. option:: CONFIG_BT_SMP_APP_PAIRING_ACCEPT

*Accept or reject pairing initiative*

Type: ``bool``

Help
====

When receiving pairing request or pairing response query the
application whether to accept to proceed with pairing or not. This is
for pairing over SMP and does not affect SSP, which will continue
pairing without querying the application.
The application can return an error code, which is translated into
a SMP return value if the pairing is not allowed.

Direct dependencies
===================

\ :option:`BT_SMP <CONFIG_BT_SMP>` && \ :option:`BT_CONN <CONFIG_BT_CONN>` && \ :option:`BT_HCI_HOST <CONFIG_BT_HCI_HOST>` && \ :option:`BT_HCI <CONFIG_BT_HCI>` && \ :option:`BT <CONFIG_BT>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Kconfig definition
==================

.. highlight:: kconfig

At ``subsys/bluetooth/host/Kconfig:358``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:34`` → ``subsys/Kconfig:9`` → ``subsys/bluetooth/Kconfig:239``

Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Security Manager Protocol support

.. parsed-literal::

    config BT_SMP_APP_PAIRING_ACCEPT
    	bool "Accept or reject pairing initiative"
    	depends on \ :option:`BT_SMP <CONFIG_BT_SMP>` && \ :option:`BT_CONN <CONFIG_BT_CONN>` && \ :option:`BT_HCI_HOST <CONFIG_BT_HCI_HOST>` && \ :option:`BT_HCI <CONFIG_BT_HCI>` && \ :option:`BT <CONFIG_BT>`
    	help
    	  When receiving pairing request or pairing response query the
    	  application whether to accept to proceed with pairing or not. This is
    	  for pairing over SMP and does not affect SSP, which will continue
    	  pairing without querying the application.
    	  The application can return an error code, which is translated into
    	  a SMP return value if the pairing is not allowed.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*