ReportServer comes with a flexible authentication mechanism that can be extended via ReportServer’s hookable plugin infrastructure. In the latest addition to our tutorial section we discuss how authentication works behind the scenes and what steps are necessary to extend ReportServer to use your custom authentication scheme.

• Tutorial: An Introduction to Custom Authenticators

We hope you find this latest addition useful and are looking forward to hearing your thoughts and comments.

ReportServer is available in numerous languages, however if you like to add a new language, or improve one of the existing translations, this document outlines the necessary steps.

Read more…

In recent posts we already outlined the necessary steps to support additional databases in ReportServer. Today we will add to this series the script that allows to connect ReportServer with a Sybase database.
Read more…

In this post we will show the necessary steps to connect ReportServer to an Active Directory using LDAP. As there are many valid ways to organize a company’s directory (may it be AD or another vendors product) ReportServer does not come with a predefined LDAP connector. This on one hand means, that the configuration might seem rather complex, but on the other hand it provides you with a maximum of flexibility.
Read more…

In our last post we have outlined the general process on how to add support for additional databases to ReportServer. Today we will give another example by explaining the necessary steps on how to access a Vertica database with ReportServer.

Read more…

By default ReportServer is shipped with support only for the most common database systems, although it can interact with virtually every database, that offers a JDBC compliant driver. In this post we will show how to develop a groovy script that adds support for the firebird database (www.firebirdsql.org) to ReportServer.

Read more…