Web Applications using Claims authentication require an update

Recently we have created a web application using claims authentication and after few days, we have noticed an error in the health analyzer as mentioned below:

ERROR MESSAGE: Web Applications using Claims authentication require an update.

You don't need to research on this error as there is an official documentation has already been published by Microsoft. – Thank you MS.

Here is the link:

http://technet.microsoft.com/en-us/library/ff686815%28v=office.14%29.aspx

To download the update, go to

KB979917 - QFE for SharePoint issues - Perf Counter fix & User Impersonation.

Additional notes:

1.   Download the Windows6.1-KB979917-x64.msu (Win7) update (for Windows Server 2008 R2).

2.   Copy the setup to all your SharePoint servers -> Install it one by one.

3.   Once the install is finished then please restart all the servers.

4.   Once all the servers are up and running

5.   Click 'Reanalyze Now by means of health analyzer list

6.   The error shouldn't be there in the list!

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

IMP NOTE:

If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

Product applies to:

1.   SharePoint Server 2010

2.   SharePoint Foundation 2010

Configuring Facebook Authentication in SharePoint 2010

Hi Guys ,

One of the most used login is Facebook . Nowadays almost everyone has a facebook account. So was checking if it possible to use the same as Authentication for the SharePoint site.

I have not yet tried this at my end Due to some Limitations However found this Step by Step Instructions very interesting and Helpful .

http://ovaismehboob.wordpress.com/2011/09/07/configuring-facebook-authentication-in-sharepoint-2010

 Thanks Ovais Mehboob .

Authentication vs. Authorization: A gereral Tip.

It is easy to confuse the mechanism of authentication with that of authorization. In many host-based systems (and even some client/server systems), the two mechanisms are performed by the same physical hardware and, in some cases, the same software.

It is important to draw the distinction between these two mechanisms, however, since they can (and, one might argue, should) be performed by separate systems.

What, then, distinguishes these two mechanisms from one another?

Authentication is the mechanism whereby systems may securely identify their users. Authentication systems provide an answers to the questions:

• Who is the user?
  
• Is the user really who he/she represents himself to be?

An authentication system may be as simple (and insecure) as a plain-text password challenging system (as found in some older PC-based FTP servers) or as complicated as the Kerberos system described elsewhere in these documents. In all cases, however, authentication systems depend on some unique bit of information known (or available) only to the individual being authenticated and the authentication system -- a shared secret. Such information may be a classical password, some physical property of the individual (fingerprint, retinal vascularization pattern, etc.), or some derived data (as in the case of so-called smartcard systems). In order to verify the identity of a user, the authenticating system typically challenges the user to provide his unique information (his password, fingerprint, etc.) -- if the authenticating system can verify that the shared secret was presented correctly, the user is considered authenticated.

Authorization, by contrast, is the mechanism by which a system determines what level of access a particular authenticated user should have to secured resources controlled by the system. For example, a database management system might be designed so as to provide certain specified individuals with the ability to retrieve information from a database but not the ability to change data stored in the datbase, while giving other individuals the ability to change data. Authorization systems provide answers to the questions:

• Is user X authorized to access resource R?
  
• Is user X authorized to perform operation P?
  
• Is user X authorized to perform operation P on resource R?

Authentication and authorization are somewhat tightly-coupled mechanisms -- authorization systems depend on secure authentication systems to ensure that users are who they claim to be and thus prevent unauthorized users from gaining access to secured resources.