I don't have strong feeling on this either way. -----Original Message----- From: Scott Golightly [mailto:[email protected]] Sent: Thursday, April 09, 2009 2:29 PM To: Stonehenge Development Subject: RE: Integrated Authentication for dotet SetupActions
If it is just for the setup then I don't see a problem. It could simplify the setup as well since you wouldn't have to add the sa password to app.config but you would still need to verify/update dbserver value. Scott Golightly > From: [email protected] > To: [email protected] > Date: Thu, 9 Apr 2009 17:25:14 -0400 > Subject: RE: Integrated Authentication for dotet SetupActions > > The change I was planning is only related to the SetupActions class for > windows auth, there's code in there now that isn't implemented. You'd still > have the DB setup for SQL auth, it just keeps you from having to know the sa > password. > > The services would still use the SQL Auth with user trade/yyy. > > > > -----Original Message----- > From: Scott Golightly [mailto:[email protected]] > Sent: Thursday, April 09, 2009 5:17 PM > To: Stonehenge Development > Subject: RE: Integrated Authentication for dotet SetupActions > > > I think SQL AuthN is a holdover from the original StockTrader that was > patterned after and using the same functionality as the IBM StockTrade 6.1 > applicaton. We may not need it for setup but for the current application we > need it to run the app. > > I don't see why the setup couldn't use integrated authentication but we will > still need to have SQL AuthN turned on since the services are not hosted in > IIS with a definite user id and so should probably still use SQL AuthN. The > alternative to SQL AuthN would be to make sure that the user that is running > the services (most likely administrator since we are running in an elevated > command prompt) is added to SQL as a user in the database. If we are still > going to have to use SQL AuthN we need to ensure that the sa account is set > up with a password (hopefully strong) and we will still need the trade user > in the database. > > I don't think we should change the application to use integrated > authentication because that would prohibit some of the other implementations > from calling the SQL Server database. > > > > Scott Golightly > > > From: [email protected] > > To: [email protected] > > Date: Thu, 9 Apr 2009 16:45:33 -0400 > > Subject: Integrated Authentication for dotet SetupActions > > > > Guys, > > > > Is there any reason why the SetupActions Integrated Windows Authentication > > is set to Empty? > > > > I just ran a test, I had to change the code in a few other locations, but I > > got it working in Integrated Auth mode. Can I create a patch for this, it > > will be helpful to have use this mode for the Express Installation guide. > > > > Ben Dewey > > Senior Software Developer > > > > twentysix > > NEW YORK > > 62 West 45th Street, 5FL > > New York, NY 10036 > > T (212) 840 0008 > > F (212) 840 9490 > > www.26NY.com<http://www.26NY.com> > > > > Heard about Microsoft SQL Server 2008 and want to know more? > > Register for Andrew Brust's Webcast OLAP Development Using SQL Server > > 2008<https://www.clicktoattend.com/invitation.aspx?code=133837> > > Check our Web site<http://26ny.com/content/4.2_events.html> regularly for > > other topics and dates > > > > Microsoft Gold Certified Partner > >
