How do I connect to the OneAegis (f/k/a IRBManager) Reporting Server

Overview

The Reporting Server add-on provides clients with an authenticated, encrypted, read-only connection to their data for use with standard 3rd party reporting tools, such as Tableau, Crystal Reports, SSRS, or even custom code.

Any tooling that can read Microsoft SQL Server databases should work with the Reporting Server,. However, support for 3rd party tools is not part of the service, you need to know how to use the tools. Also, this is an optional component of your subscription, these instructions will not work if you do not have this add-on as part of your subscription. Contact your sales representative for more information on adding this option.

Connecting

To connect you want to setup your reporting tool as you would for any standard connection to SQL Server. The server name is "reportingserver.oneaegis.com" (you can continue to use reportingserver.irbmanager.com too), using the standard SQL Server TCP port of 1433. It is not necessary to select encryption, we force encryption from our end, but there is no harm in selecting it either -- to clarify, the connection is always encrypted regardless of whether you select encryption. We have seen some client's IT departments block outbound TCP/1433. If you cannot connect make sure your IT allows outbound TCP/1433 connections.

For the username use your Client-ID and then your OneAegis username, separated by a backslash. For example, if your Client-ID is GreatHospital and your username is CoolUser@GreatHospital.com you want to use "GreatHospital\CoolUser@GreatHospital.com" as the username for the server. The password is your OneAegis password. For users with SSO logins, to access Reporting Server you need to use your OneAegis-native password, not your SSO password. 

Access

Any user that will connect to the Reporting Server must be part of the "api-access-ReportingServer" group in OneAegis. Only members of this group will be allowed to connect. Users do not need any special authority beyond membership in this group to connect to Reporting Server. Additionally, Reporting Server queries run directly against the database and are below our application security layer. Reporting Server users have the ability to view all data in your OneAegis client.

If you are running personal reports you can just use your personal username, but if you are scheduling or automating we recommend creating a dedicated reporting user (or users) for this use. These users do not need to have any special permissions beyond membership in the api-access-ReportingServer group mentioned above.

Certificate Errors

We use a self-issued certificate for Reporting Server. This does not impact security in any way, but does mean you may need to "trust" our certificate. For SQL Server Management Studio (SSMS) the screen shot below shows how to trust the certificate. For other tools you'll need to find the equivalent option to trust the certificate.