<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
<!-- This component and the accompanying materials are made available under the terms of the License 
"Eclipse Public License v1.0" which accompanies this distribution, 
and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
<!-- Initial Contributors:
    Nokia Corporation - initial contribution.
Contributors: 
-->
<!DOCTYPE concept
  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept xml:lang="en" id="GUID-C670D31C-82A7-519C-8506-3C4B99294B21"><title>Bluetooth Security Manager overview</title><prolog><metadata><keywords/></metadata></prolog><conbody><section><title>Purpose</title> <p>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. </p> <p>Note that the API only deals with incoming connections: for outgoing services, see <xref href="GUID-4F0C4B9D-AA42-59C4-900A-7045FEAAF2F4.dita">How to use security on outgoing sockets</xref>. </p> </section> <section><title>Architectural relationships</title> <p>The API uses the <xref href="GUID-D0D27AEA-FDDB-5F6F-94F6-ADDF5910DC47.dita">client/server</xref> framework. The API provides <codeph>R</codeph> classes that send requests to a server process that stores and manages security information. </p> </section> <section><title>Description</title> <p>Before using the security manager, clients must open a session to it using <xref href="GUID-B7CBABF9-93A1-3275-9CB0-CDF8A6606BB1.dita"><apiname>RBTMan</apiname></xref>, and then a subsession using <xref href="GUID-D536FA83-2535-3BF2-AC0D-EA0C7CA806BA.dita"><apiname>RBTSecuritySettings</apiname></xref>. </p> <p>A security settings object, <xref href="GUID-BC29B643-2CE8-30C1-BF41-4D2B5585DC81.dita"><apiname>TBTServiceSecurity</apiname></xref>, is used to set whether authentication, authorisation, and/or encryption are required. </p> </section> </conbody></concept>