[chortler]

I'm trying to set up a blackberry to use a Blue tooth enabled virtual keyboard, and I need allow the blackberry to use the injector API. I can't use the handheld configuration tool as the BES server isn't local?

Any ideas?

[jonberry]

If you are on a BES, I'm pretty sure the only way is to have the BES admin adjust the policy.

BTW, I think this default policy is a little excessive, but I understand RIM's concern; they just need to find better solution to the problem so that the API can be used without any security risk.

Let us know if you find another way to make this work...

Jon

[wistowg]

I am the admin of a 9 server, 1000+ user BES 4.0 environment and cannot enable these bluetooth keyboards to access the API Injector. Software config policy is correctly set to allow on the BES but the handheld is always set to Deny. If anyone's succeeded in a BES environment, I'd love to know what the trick is.

[jonberry]

I think the default on Handheld software 4.1 is to not allow the Injector API.

So it may be that each individual user will need to adjust their security settings manually even if you have allowed the policy on the BES.

What does the keyboard manufacturer have to say about this?

[morrison23]

I'm trying to set up bluetooth keyboards as well and can't figure out how to do it. I've got BES 4.x admin rights, many different devices to test with (7200's 8700's, etc.).

The manufacturer's instructions are so cryptic I can't make any sense of them.

Has anyone out there done this before? I've got two different manufacturer's keyboards, although they appear to be exactly the same devices. One is from freedom input.

[mauiboy]

Some information that might help.

About the Injector error message. BlackBerry devices implement high security profiles. This is both Good for security and Bad for user that want to connect Bluetooth keyboards.

However newer devices such as 8700, 7130, etc has on-device security profile control configuration. But before you can use it, first you need to determine if your BlackBerry EMAIL is connected using BES.

IF NO (Not using BES) THEN

The device security profile needs to allow keyboard driver the use of the Injector API. Follow the steps below:

1. Open [Options].
2. Open [Advance Options\Applications\Modules]
3. Highlight [Driver] application
4. Select [Edit Permissions]
5. Select [Interactions]
6. Select [Change Option]
7. Select [Allow]
8. Exit and Save


IF YES (using BES) THEN

Unfortunitely if your email uses BES you have to setup security profile on the BES. but before that only BES 4.0 and higher allow you to setup security profile. if you have 3.7 BES you can not use Bluetooth keyboards.
here is all the info you would need.

Please read this thread:
http://www.blackberryforums.com/showthread.php?p=179315

To enable Event Injection for the third-party application, the BlackBerry Enterprise Server administrator can perform the following steps:

0. Install keyboard driver on to the BES server.
1. From the BlackBerry Enterprise Server, open the BlackBerry Handheld Configuration Tool.
2. In the left pane, click Software Configurations.
3. Select a software configuration and click Edit Software Configuration.
4. Click Add New Configuration.
5. Enter a name for the new configuration and enter a description (optional).
6. Enter the Handheld Software Location in standard UNC format or select the Change button to browse to the location of the Program Files\Common Files\Research In Motion\ directory that was shared in the steps above. For more detailed information on Handheld Software Configurations, see the section entitled, xxx8220;Defining Handheld Software Configurationsxxx8221; in the Handheld Management Guide.
7. Click the Policies button.
8. Select a policy from the left pane and click the Properties button, or create a new policy by clicking the New button.
9. Find the label for Event Injection and change the value to Allowed.
10. Click OK to dismiss the policy properties screen.
11. Click OK to dismiss the policies screen.
12. Expand the Application Software tree.
13. In the Policy column, use the drop-down list to select the policy that allows Event Injection for the desired third-party application. Or, select the policy at the end of the row in order for the tree to apply the policy to all third-party applications.

[wistowg]

Found the answer to this - when you set-up the software configuration on the BES you have to set the Keyboard Injection policy to Allow BEFORE you click OK to the existence of the bare bones policy itself. Trying to edit the keyboard injector settings afterwards doesn't work