Ben clarified that he is just going to make the change for the setup and that it will still work with SQL authentication so we will not be forcing any changes, just enabling a simplified setup when running as an administrator on Windows. This will maintain interoperability at the database level if desired.
Scott Golightly > From: [email protected] > To: [email protected] > Subject: RE: Integrated Authentication for dotet SetupActions > Date: Thu, 9 Apr 2009 22:01:22 +0000 > > Does forcing integrated security cause a problem if we have a situation of > WSO2 or Sun's version running on Linux and wanting to talk to SQL Server? I > think the original StockTrader showed interop at the database level as well, > but I don't know how important it is that we maintain that for Stonehenge > (since WS-* interop is the main purpose here). > > I would like WSO2 input/agreement before we change it. > > Kent > > -----Original Message----- > From: Scott Golightly [mailto:[email protected]] > Sent: Thursday, April 09, 2009 2: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 > >
