none
Restoring a PWA instance to a Web Application with a different authentication mode RRS feed

  • Question

  • Hello,

    I have the following problems: a PWA instance was created in a web app that was incorrectly set up to use claims authentication (Project Server 2010). People have worked at configuring the environment as the mistake was only noticed much later. The problem is, at some point the databases are supposed to be deployed in an environment using classic authentication.
    I tried to change the configuration by doing the following:
    - Deleting the PWA instance
    - Deleting the Web App
    - Creating a new Web App in classic mode
    - Associating the content DB to the new Web App
    - Creating a new PWA instance (using the DBs from the previous PWA) in the new Web App

    I get various errors depending on whether or not I try to keep the content DB or whether I try to restore to the same URL or not. But before I get too deep in troubleshooting or alternative scenarios, my question would be: is it possible at all to do what I'm trying to do (switching a PWA instance from claims mode to classic mode)? Has anyone tried it before?


    Friday, March 9, 2012 12:20 PM

Answers

  • Livia,

    Apparently in MS wisdom, moving from Windows Auth to Claims Auth is a one way street.  Using PowerShell, you may go From Windows Auth TO Claims Auth.

    however, you cannot go back.

    See this posting for some potential workarounds : http://sharepointegg.blogspot.com/2011/01/reverting-claim-based-authentication-to.html 

    I have successfully gone from Windows Auth to Claims in PWA even just recently, but I have not tried to "go back"...

    BTW: Claims is the MS preferred authentication setting and PWA works just fine with this setting ... I think there is one exception, that escapes me right now...

    you did not say why you need to do this...what is the real issue you are having?

    I have been setting up PWA for many clients using Claims Authentication with Windows Authentication Active and NTLM as the only option.

    True - you see the odd chars on the login names, but all else appears to work as desired.

    let us know the underlying problem that you are facing...


    Thanks, Eric S. http://www.pcubed.com

    Sunday, March 18, 2012 11:16 PM

All replies

  • Livia,

    Apparently in MS wisdom, moving from Windows Auth to Claims Auth is a one way street.  Using PowerShell, you may go From Windows Auth TO Claims Auth.

    however, you cannot go back.

    See this posting for some potential workarounds : http://sharepointegg.blogspot.com/2011/01/reverting-claim-based-authentication-to.html 

    I have successfully gone from Windows Auth to Claims in PWA even just recently, but I have not tried to "go back"...

    BTW: Claims is the MS preferred authentication setting and PWA works just fine with this setting ... I think there is one exception, that escapes me right now...

    you did not say why you need to do this...what is the real issue you are having?

    I have been setting up PWA for many clients using Claims Authentication with Windows Authentication Active and NTLM as the only option.

    True - you see the odd chars on the login names, but all else appears to work as desired.

    let us know the underlying problem that you are facing...


    Thanks, Eric S. http://www.pcubed.com

    Sunday, March 18, 2012 11:16 PM
  • Hello Eric,

    Thanks for your answer, I'm under the impression that it's not supported to revert to classic authentication and you seem to confirm this.

    The actual problem you can't help me solve: we want to install a third party add-on which does not support claims authentication yet. Should come in a future version, but for now we have to bear with it.

    Livia

    Monday, March 19, 2012 10:28 AM