Timeline for Restore Web Application issue
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 10, 2017 at 22:31 | answer | added | Greg W | timeline score: 0 | |
| Feb 10, 2017 at 22:26 | comment | added | Greg W | Ok, I'll give it a try in an answer | |
| Feb 10, 2017 at 15:51 | comment | added | Ven | Sorry to reiterate. Those are modes, but Claims can be Windows, Forms or Trusted Identity claims. It is clearly called out in the link that you provided above. "Windows accounts are converted into Windows claims. Forms-based membership users are transformed into forms-based authentication claims." Anyway, it returns True for all the web applications in my farm. | |
| Feb 10, 2017 at 11:14 | comment | added | Greg W | A Web Application can be in one of two modes, Classic or Claims, regardless of whether you're using Windows, Forms or SAML. Have a read of technet.microsoft.com/en-us/library/cc262350.aspx. What do you see when you run the following command: Get-SPWebApplication |select Name, UseClaimsAuthentication ? | |
| Feb 10, 2017 at 10:38 | comment | added | Ven | I don't think I am confused. Claims comes in 3 flavors. Windows, Forms and Trusted Provider. NTLM and Kerberos are within Windows. I restored the web application using PS command provided in the TechNet link. | |
| Feb 10, 2017 at 10:15 | comment | added | Greg W | I think you're confusing your terms. Windows authentication refers to either NTLM or Kerberos. This is completely separate from the Classic vs Claims configuration as you can have any combination of each. How did you restore your Web Application (note, this is different to restoring a site collection)? | |
| Feb 10, 2017 at 9:49 | history | asked | Ven | CC BY-SA 3.0 |