A Short Explanation of the Double-Hop Issue in SharePoint
The double-hop issue in SharePoint occurs when IIS attempts to pass the user’s NTLM credentials to a service that is running on a server that is either not part of the requesting server’s farm, or not running directly on the web server. A good example of this is a web part that requests data from a SQL server that is not part of the MOSS farm and that SQL server requires the credentials of the user making the request. This type of authentication request is disallowed in .NET. As NTLM authenticates only the client and not the server, there would be no way for the end user to know if their credentials were passed to a valid service. If Microsoft Windows authentication allowed this, a web server could collect user credentials and pass them around at will. This would be a very poor security model. Fortunately, Kerberos authentication provides a workaround for this, but it requires a little more configuration effort.
1 comment
(1 votes, average: 5 out of 5)
Loading ...Capture and Redirect HTTP to HTTPS with SharePoint 2007
SharePoint administrators are often asked to securely publish their sites either to the Internet, internally, or both. This is a fairly straightforward process of configuring your MOSS installation for SSL and publishing your site using any one of the numerous firewalls or proxy servers available on the market. But what happens if your users forget the site is SSL secured and enter http://your.moss.site instead of https://your.moss.site? Well, if you’ve properly secured your site and blocked HTTP traffic from the Internet, they receive the all too familiar 404 page not found error and you get a call asking why the site is down. If they are internal users and enter http://your.moss.site, they receive a 403.4 Forbidden: SSL is required… error.
5 comments
(2 votes, average: 4.5 out of 5) Loading ...Office Communicator 2007 and Outlook 2007 Integration Error
After installing the Office Communicator 2007 client you may have two errors indicating that there is a problem with Communicator’s integration with Outlook.
The first error refers to a required hotfix that you can download directly from the link provided in the “Information” dropdown in the Communicator client. Simply select the link in the dropdown and install the patch.
(2 votes, average: 4.5 out of 5) Loading ...