Protected Database and Reporting Services.

Note: If you grant access by login you don't need this extension.

Like any other client application, the Reporting Services server is also affected by access restrictions (if access restrictions are applied). DbDefence installs a special module that intercepts all database connections from the Reporting Services process. It executes an unlocking statement before any other SQL command from report.

The module (.NET assembly) Elitude.ReportingServices.BDataExtension.dll is automatically installed to the Bin folder of Report Server. You do not need to configure it. The same module is copied to Business Intelligence Development Studio/Visual Studio "Common7\IDE\PrivateAssemblies\" to enable access to protected databases during design time.

Installer creates an additional database source called "Connection To Protected Database". If you already have existing connections configured for SQL Server you can safely change it to "Connection To Protected Database" and leave all options unchanged.

Source "Connection to Protected Database" in web interface:

In Business Intelligence Studio:

It behaves in absolutely the same way as the Microsoft SQL Server connection and accepts the same parameters and credentials. However, it accepts additional options for unlocking database access.

This data source accepts additional parameters called bdb and bpwd. bdb specifies the name of the protected database to unlock (if it is not the current database); bpwd specifies the unlocking password. The same password is used for encryption. If Initial Catalog in the connection string is the protected database, you may omit the bdb parameter.

The extension module unlocks the database with the very first command, so all further queries from report run in unlocked databases.

Security considerations

You may want to protect the connection string itself. Please refer to Microsoft Documentation.