:orphan:

.. title:: CONFIG_BT_SMP_APP_PAIRING_ACCEPT

.. kconfig:: CONFIG_BT_SMP_APP_PAIRING_ACCEPT

CONFIG_BT_SMP_APP_PAIRING_ACCEPT
################################

*Accept or reject pairing initiative*

Type: ``bool``

Help
====

.. code-block:: none

    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
===================

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

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

Defaults
========

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

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



At ``<Zephyr Subsystem>/bluetooth/host/Kconfig:297``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:44`` → ``<Zephyr Subsystem>/Kconfig:9`` → ``<Zephyr Subsystem>/bluetooth/Kconfig:174``

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

.. code-block:: kconfig

    config BT_SMP_APP_PAIRING_ACCEPT
    	bool "Accept or reject pairing initiative"
    	depends on BT_SMP && BT_CONN && BT_HCI_HOST && BT_HCI && 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.)*