The cDir application will open connections to the BES SQL Server every time:

• When the cDir shortcut is pushed to BlackBerry devices.
• When the cDir shortcut is pushed to a predefined group of recipients.
• When BESQuery is invoked either from the server side or from the client side.

1. cDir relies only on SQL authentication. Because of this the BES SQL server should be set-up to support Mixed Authentication.
2. At installation time cDir creates the following objects in the BESMgmt database:
   • A role called cDir_DataReader
   • Two in-line functions: USR_CDIR_GET_BLACKBERRY_USER, USR_CDIR_GET_BLACKBERRY_USERS
   • The installer will grant SELECT rights to the above in-line functions to the cDir_DataReader role. [NB. in a more restricted environment this step could be skipped at installation time: the application ships with the actual SQL scripts that could be handed on to a DBA to run them manually.]
3. Our recommendation is to create a SQL Login that will be used by the cDir application to open connections to the BESMgmt database. This login at server level should be member of the Public role and at BESmgmt database level should be mapped to a User that is member of the Public role and cDir_DataReader.
4. At cDir level at configuration time, the above login should be used to set-up the SQL Connection to the BESMgmt Database. This will limit the capabilities the cDir application has at SQL level to the three in-line functions specific to the cDir application.