SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am facing a strange issue in Central Administration. I was trying to change the Authentication Type of a Web Application by following the steps, Central Administration -> Manage Web Application -> Authentication Providers -> Default -> Edit Authentication, but the "Authentication Type" option is invisible here. For other web applications it shows but for the web application that I am concerned with, does not shows. Here is the image:

enter image description here

This is missing in the above window:

enter image description here

share|improve this question

If your current Authentication Type is Windows then you see the outdated section with

  • Windows
  • Forms
  • Web single sign on

But isn't allowed to change it as the only real options are:

  • Windows
  • Claims

If your current Authentication Type is Claims then the section isn't shown.

My guess regarding the reason behind this is:

  • It was planned to give you support for changing Windows => Claims in the UI, but they didn't get it completed, so we only see an odd part in the UI
  • Changing Claims => Windows isn't supported so there should be no ui for this
share|improve this answer
Hi Jakobsen, You are absolutely correct, the Authentication Type was changed to Claim Based but now how can I revert to Windows Based authentication? – Zakir HC Jun 25 '12 at 9:33
As far as I know it's not supported. So I'd recommend deleting the WebApp (not content databases), Create new WebApp, Attach databases, change permissions. – Per Jakobsen Jun 25 '12 at 9:53
That means I have to take a backup of the Content DB and then delete the Web App and then create a new web app and restore and attach the content DB to it. – Zakir HC Jun 25 '12 at 12:21
If when deleting the Web App you leave the "Delete content databases" as No then the restore part isn't needed. (The backup is still a good idea) – Per Jakobsen Jun 25 '12 at 12:49
Isn't this solution requiring a script that call MigrateUser ? (because of the claims prefix) – Steve B Jun 26 '12 at 7:18

If you go in Security > Specify authentication providers, the result is still the same?

share|improve this answer
Hi Seb, The result is still the same. – Zakir HC Jun 25 '12 at 9:31

Thanks all for your replies and answers.

I also found two solutions:

  1. Delete the web application without deleting the content database, then create a new Windows authenticated web application and connect the new web application to the old content database. (This was already advised by @Per Jakobsen above)

  2. Use the script below to change Claim Based Authentication to Classic mode authentication. “Authentication Type” section will be visible in the “Edit Authentication” page after you run the commands. In this method, the existing sites will be inaccessible with the old credentials. You need to set up all the accounts for Windows authentication from scratch.

           $setcba = Get-SPWebApplication "http://YourSiteURL"
           $setcba.UseClaimsAuthentication = 0;

You should backup the web application before either of the actions above to avoid any data loss and make sure we can go back to the current state.

Thanks & Best Regards,

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.