View Complete Post
We've setup an intranet site using Windows Integrated Security. Its up and running and users can access it. However, they are being challenged with a login dialog for the server when they initially access the site.
Isn't is possible to configure the server so that the users aren't challenged AND are recognized as being already authenticated by Windows? We're trying to go with a seamless experience, whereby all they have to do is login to their machine like normal and then go from there.
Microsoft security expert Bryan Sullivan believes denial-of-service blackmail attacks will become more common as privilege escalation attacks become more difficult to execute. He demonstrates how to protect your apps against regular expression DoS threats.
MSDN Magazine May 2010
This article reviews what makes XML vulnerable to denial of service attacks and how to mitigate these attacks.
MSDN Magazine November 2009
A Security Token Service, or STS, acts as a security gateway to authenticate callers and issue security tokens carrying claims that describe the caller. See how you can build a custom STS with the "Geneva" Framework.
Michele Leroux Bustamante
MSDN Magazine January 2009
I get loads of security questions from friends and former students, and recently I've gotten a number of questions about building secure data-driven Web sites for internal enterprise systems. I've decided to answer them here to hopefully save you some headaches in your own projects.
MSDN Magazine September 2005
The .NET Framework 2.0 provides custom credentials management to ASP.NET apps out of the box. Using it, you can easily authenticate users without using Windows accounts. In this article the author presents a set of helper classes that let a Windows Forms application use the ASP.NET credentials management infrastructure as easily as if it were an ASP.NET application.
MSDN Magazine April 2005
MSDN Magazine September 2002
This article completes the .NET Framework overview begun in the September issue. The common language specification and ILDasm, the MSIL disassembler, are discussed-as well as how metadata, manifests, and assemblies simplify deployment and versioning. Security, which is integral to the design of .NET, is examined extensively, followed by a walk through the development of a single assembly containing multiple files. Finally, the way managed and unmanaged code work together, and the benefits of using each, including interoperablity with unmanaged code, are described.
MSDN Magazine October 2000
The Microsoft .NET Framework is a new platform for building integrated, service-oriented applications to meet the needs of today's Internet businesses; apps that gather information from, and interact with, a wide variety of sources, regardless of the platforms or languages in use. This article, the first of a two part series, illustrates how the .NET Framework enables you to quickly build and deploy Web services and applications in any programming language. Microsoft Intermediate Language and JIT compiler, which make this reuse possible, are described as well as managed components, assemblies, and the Common Type System (CTS).
MSDN Magazine September 2000
When trying to publish an InfoPath 2007 form template (as a Content Type), I am getting the following message with a UserName/Password dialog box:
Enter your credentials to connect to the following web service:
When I enter my credentials, the above dialog box appears again. I have carefully entered my credential. Another thing I noticed that despite this error I see the form got created at the destination library. The only thing is that the Content Type did not
get created and hence is not available in the "Site Content Type Gallery".
We are using Sharepoint 2007 enterprise edition. And I have recently published the InfoPath form templates several time as Content type without any issue.
Please help. Thanks........
I have a serious problem that cannot be solved by googling around the keywords below: sharepoint, moss 2007, reporting service, ssrs 2008, rendering, internal server error, ....
The error is;
"An error occurred during client rendering. The remote server returned an error: (500) Internal Server Error. "
Everything is O.K.;
* When I render the report from the REPORTSERVER (http://localhost/ReportServer) * When the reports are scheduled to be sent by the reporting service (planned via MOSS 2007)ÃÂ
But if I open (render) the RDL file from the sharepoint REPORTS LIBRARY interface, all of the reports fail with that internal error message above.ÃÂ
It is weird also that parametrized reports are displayed without errors although the parameters are queried from a sql dataset. But I got the error when rendering the report after I've chosen a parameterÃÂ and order "apply/report"...
Possible causes how I met that error may be;
After I have installed (then uninstalled) AJAX extensions After I have re-configured IIS Web Service Extensions list items
Possible solution alternatives I've found;
I've found a solution on MSDN replying a similar issue with an ideal cause of the error but an evreka answer but no sol
I have a web service that is accessed by a windows forms application and receives updates like facility name, address, image etc. Everything works fine except the image data is not being passed to the windows app. I am saving the images in database on both sides, so when I pull it from the server I use the following code
facility.FloorPlan = (
I can see the facility.FloorPlan Dimentions as 103840 when I debug this method which means that the data is pulled from the database fine.
On the forms side though the dimentions become 0, all other values pass fine except this. Here is the facility property in the web service on server side.