Description
Services that need ask the user to accept/reject an operation such as accept OBEX objects or accept an incoming connection can use the Security API to request the userspace registered authorization agent responsible.
Development warnings/recommendations
- Just one Authorization request per time is allowed.
- NotConnected error is returned if a connection is not found between the devices is not found.
Trusted Devices
The BlueZ daemon keeps a list of trusted devices. Trusted means that authorization is not required to accept incoming connections or other operations that need the user response. Once a given device is added to the list, the BlueZ daemon will reply authorized without call the Authorization agent.
Authorization Agent
Authorization agents are applications responsible for address authorization requests. For more information check the BlueZ D-Bus API and implementation references:
- utils/daemon/auth-agent.c is a authorization agent implementation able to handle device specific and default
- bluez-gnome passkey/authorization agent implementation distributed by the BlueZ community
Canceling
For security reason, only the requestor can cancel a pending authorization operation.
