Bluetooth Security Manager overview

Purpose

Enables Bluetooth services to set appropriate security requirements that incoming connections to that service must meet. Security settings are simply whether authentication, authorisation, and/or encryption are required or not.

Note that the API only deals with incoming connections: for outgoing services, see How to use security on outgoing sockets.

Architectural relationships

The API uses the client/server framework. The API provides R classes that send requests to a server process that stores and manages security information.

Description

Before using the security manager, clients must open a session to it using RBTMan, and then a subsession using RBTSecuritySettings.

A security settings object, TBTServiceSecurity, is used to set whether authentication, authorisation, and/or encryption are required.