To test out the migration of a site from SharePoint 2010 to 2013, I needed to convert a test environment web application to claims authentication to prepare for the move. However, to prove out my methodology and make sure I had the process down, I converted the web app back to classic authentication in order to repeat my steps. I’ve found a number of sites that explain how to do this, but have yet to find it all consolidated into one post. So here’s what I’ve found.
Tag: Authentication
If you’re ever in need of converting your existing web applications within SharePoint to claims authentication from classic auth, you’ll need to run the following commands.
In order to do this, you’ll need to use the SharePoint PowerShell command prompt and run the commands in the order below under your farm service account:
For future reference. This came in very handy after I turned on Google 2-step verification. Originally found here: http://passion4high-tech.blogspot.com/2013/03/postfix-sasl-authentication-failed-with.html
————————————–
If you configure your Google account for extra security to use the 2-step verification, then some applications which work outside the browser might not be compatible with 2-step verification and cannot ask for verification codes.
Postfix which was installed and configured to send out emails won’t work anymore, and you might notice error messages in the /var/log/mail.log file.
Something like:
SASL authentication failed; server smtp.gmail.com said: Application-specific password required.
The solution below should fix this issue: