Authentication and Security
Authentication and Security
This topic documents the issues involved with authenticating users and providing security when importing speech application data from event trace log (.etl) files, using Call Viewer and Speech Application Reports, and using the subscription and delivery features of Microsoft SQL Server 2000 Reporting Services. The following illustration shows the relationship between the components discussed in this article.
.gif)
Authenticating Call Viewer Users
In order to use Call Viewer to analyze calls which have been imported into a SQL Server database, the account used to connect to the database must have sufficient permissions to view the Call Viewer database in SQL Server. For more information on connecting to a database with Call Viewer, see the topic Viewing Calls. The minimum role to which a user must be assigned is db_datareader. For more information on using predefined roles in SQL Server, see the topic Adding a Member to a Predefined Role in the MSDN Library.
Authenticating Speech Application Reports Users
By default the reports deployed to Reporting Services at the end of the database import task are configured to use Windows authentication when connecting to the reports database. However, once the reports (.rdl) are uploaded the administrator may change the authentication and security settings of the shared datasource to whatever is most appropriate for end users of the reports. For example, the administrator may choose to use SQL Server authentication or stored credentials. One reason for changing authentication schemes is that the subscription feature in Reporting Services requires SQL Server authentication. To get the subscription service to work, in the Speech Application Reports folder, edit the Speech Reports Datasource so that it has the appropriate permissions to access both SQL Reporting Service and the reports database.
The Microsoft Speech Server log import task and the MSSLogToDatabase command-line tool connect to Reporting Services using a Web Service. If the security of this connection is a concern, using secure hypertext transfer protocol (HTTPS) is an option. If using HTTPS, Reporting Services must be configured to use the SSL (Secure Sockets Layer) protocol. For more information see the topic Configuring Server Security.