Trusted Connection - C# Console App

Question

I have been developing a C# Console Application in VS2008, and am having trouble figuring out how to use a Trusted Connection when generating the report, rather than passing it my SQL Authentication username and password.  It's connecting to SQL Server 2005. ODBC (RDO).
As of now, the application runs the report with two dates being passed, then exports it as a PDF. It works when passing it the connectioninfo, but how can I make it windows authenticated? I have used the following lines to get it to work using SQL authentication.
crConnectionInfo.ServerName = "server";
crConnectionInfo.DatabaseName = "db";
crConnectionInfo.UserID = "user";
crConnectionInfo.Password = "pass";
Edited by: djhorn on Feb 1, 2010 5:28 PM

Answer 1

Running CR XI with .NET 2008 gives me the ebee jeebes. All kinds of problems will come down eventually for you. Honest. (Reports created in CR XI and run with CR 10.5 are OK as long as you are not using features that are not present in CR 10.5 (dynamic parameters, LOVs, etc.)).
10.5 is OK, but integrated security is not handled by the report (or the CR APIs) as such. It is handled by the app / process which you will have to run under a system account that could validate the users. If the database is on a different server than the app, this constitutes a double hop and will not work. The Article I referenced (https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b021e47e-be1d-2b10-c6b2-efa9db3abd6b) applies to CR 11.5 as well as CR 2008 (v 12.x). So, for you going to CR 2008 may be the best option(?). An eval of CR 2008 is available from here:
http://www.sap.com/solutions/sapbusinessobjects/sme/freetrials/index.epx
Ludek