Guest

Cisco Unified MeetingPlace

MeetingPlace Web SQL Account Requirements for Database Access Authentication

Document ID: 51301



Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Installation Rights
Ongoing Rights
Server and Database Roles
      Server Roles
      Database Roles for the MPWEB Database
Related Information

Introduction

Cisco MeetingPlace Web uses a Structured Query Language (SQL) database and therefore requires Microsoft SQL Server to function properly. In previous releases, customers that install the product are only prompted for the location of the SQL server: local or remote. The installer always defaults to Use SQL authentication and Use the ‘sa’ account with a blank password for access authentication to the Cisco MeetingPlace Web database.

Because Use the ‘sa’ account with a blank password is Microsoft SQL Server’s built-in administrator account, the use of this account poses serious security concerns to our customers.

In Cisco MeetingPlace Web release 4.2.7 and later, you can specify your own SQL account (if you use the full SQL Server) or use the ‘sa’ account but change its password (if you use the Microsoft Data Engine [MSDE] bundled with the Cisco MeetingPlace Web installation program).

Note: The Cisco MeetingPlace Web installation program does not verify the existence of the SQL account or the validity of its user name and password combination. It is your responsibility to verify that the SQL account that you plan to use exists before you install Cisco MeetingPlace Web.

The SQL account that you create for use with Cisco MeetingPlace Web must conform to the access rights described in this document.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on Cisco MeetingPlace Web version 4.2.7 and later.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Installation Rights

During the installation of Cisco MeetingPlace Web, you are prompted to enter a SQL Server user name and password. This SQL Server user must have the right to be able to log in to the SQL Server instance specified during the installation. Further, that user must have the these additional rights:

  • Create Database

  • Create Table

  • Create Default

Ongoing Rights

After the installation is complete, you may remove this right from the SQL Server user:

  • Create Database

The user must have these rights for all tables in the MPWEB database:

  • Select

  • Insert

  • Update

  • Delete

Note: The user, thus, still needs to be able to alter the MPWEB database.

Server and Database Roles

SQL Server provides some useful built-in roles that make it very simple to grant and deny rights. The simplest way to create a user with the proper rights for Cisco MeetingPlace Web is to create a user and assign that user these roles:

Server Roles

  • dbcreator

Database Roles for the MPWEB Database

  • public

  • db_datareader

  • db_datawriter

  • db_ddladmin

  • db_owner

Because you can not assign database roles until after the database is created, you must wait until after Cisco MeetingPlace Web finishes its installation to assign the roles. Then, use the SQL Server Enterprise Manager to assign the roles.

Note: You might receive this error:

Error 21776: [SQL-DMO] The name 'dbo' was not found in the Users collection.
If the name is a qualified name, use [] to separate various parts of the name,
and try again.

If you received that error, you must first change the owner of the MPWEB database; issue this command to launch a procedure that is stored in the MPWEB database:

exec sp_changedbowner 'sa'

This problem and its workaround are documented in Microsoft Knowledge Base Article 305711, BUG: DBO User Does Not Display in Enterprise Manager leavingcisco.com.


Related Information



Updated: Jan 31, 2006 Document ID: 51301