Security settings

Bluetooth API security model implemented in Java platform for S60 is based on MSA version 1.00 security policy.

Permissions are required for opening Bluetooth and OBEX client and server connections. These permissions are granted basing on the Local Connectivity function group. Permission is also required when a push MIDlet is registered to PushRegistry and when push MIDlet is to be launched. This permission is granted basing on Application Auto Invocation function group.

For Identified Third Party Protection Domain and Unidentified Third Party Protection Domain MIDlets the user settings are defined according to Table 2.

**Table:** Table 2. User settings for Local Connectivity and Application Auto Invocation function groups.
Function group	Identified Third Party Protection Domain		Unidentified Third Party Protection Domain
	Default setting	Other settings	Default setting	Other settings
Local Connectivity	Session	Blanket, Oneshot, No	Oneshot	Blanket, Session, No
Application Auto Invocation	Oneshot	Blanket, Session, No	Oneshot	Session, No

Explanations for Table 2 values are as follows:

“Blanket” is valid for every invocation of an API by a MIDlet suite until it is uninstalled or the permission is changed by the user.
“Session” is valid from the invocation of a MIDlet suite until it terminates. “Session” mode MUST prompt the user on or before the first invocation of the API or function, which is protected. When the user re-invokes the MIDlet suite the prompt MUST be repeated.
“Oneshot” MUST prompt the user on each invocation of the API or function, which is protected.