Telerik Report - Implementing SQL Data Source using Connection String with Managed Identity

[Nikhil]

I have my SQL Server on Azure Virtual Machine. I'm trying to use Managed Identity Connection String (without the need of username, password in the connection string) to connect my SQL Server with Telerik Report. I did not find any specific documentation or a question regarding this implementation. Any leads will be appreciated.

I can connect my SQL Server using this normal connection string: Server=tcp:sqlserverendpoint,1234;Initial Catalog=SampleDatabase;Persist Security Info=False;User ID=username;Password=password;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;

I'm trying to use this Connection String (which doesn't include username and password): Server=tcp:sqlserverendpoint,1234;Authentication=ActiveDirectoryManagedIdentity;Encrypt=True;Database=SampleDatabase;

Any leads would be appreciated. Thanks.

[Dimitar]

Hello Nikhil,

Thank you for the provided information!

To use the new connection string format, it is necessary to install and use the new Microsft.Data.SqlClient data provider because the older provider does not support it.

You may have a look at the System.Data.SqlClient Conversion overflows errors within reports in Reporting | Telerik Forums forum post for details on how to enable the new data provider.

Please test installing the new provider and let me know if you need additional assistance.

Regards,
Dimitar
Progress Telerik

[Brian]

What about MsSqlServerStorage? Can this be used with Microsoft.Data.SqlClient?

 

I see from the decompiled code that "using System.Data.SqlClient" is in the code for the class.

 

Is there are way to to change this?

[Dimitar]

Indeed, the MsSqlServerStorage implementation currently uses the System.Data.SqlClient data provider. Unfortunately, it is not possible to change the provider since its used internally in our code, however, it would make sense to migrate the new provider in the future so I have logged a FR on your behalf - Migrate MsSqlServerStorage to use the new Microsoft.Data.SqlClient (telerik.com).

Curerently, the only workaround would be to create a custom MS SQL Server storage that uses the Microsoft.Data.SqlClient provider by implementing the IStorage interface.

Please let me know if you have any other questions.