Implications of switching to Claims Based Authentication

I need to switch to Claims Based Authentication to get my 2FA application protecting our Sharepoint site correctly.
Are there any negative implications to the configuration of just changing it?
Will in impact on anything else?
Sorry to be so vague.
David_J_GAsked:
Who is Participating?
 
KoenVostersCommented:
The only issues I've seen in the past have been with custom applications that use code that works with strings to do funky things to identify the user by the loginname. Other than that, I haven't really seen any issues. The one thing that does not work with claims based authentication is the document preview with FAST search (at least in 2010, in 2013 it's the other way around)

Just make sure you have a backup of your content database so that if needed you can recreate the web application with classic mode authentication and reattach the content database.
0
 
KoenVostersCommented:
I could write it all down here on what to do (and the impact) but there is a great technet article that explains it all:

http://technet.microsoft.com/en-us/library/gg251985.aspx
0
 
David_J_GAuthor Commented:
Thanks for the link KoenVosters.

I'm not really up to speed with powershell etc but an interesting and useful document.

I could not see any real statements in it about any downsides to moving from classic mode to CBA.

Are there any?
0
 
David_J_GAuthor Commented:
Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.