Who is this article for?

  IT Administrators who want to change the desktop client authentication method.

  IT Administrator permissions are required to make this change.

This article describes the steps required to change the authentication method used by the desktop client from Windows authentication to FBA.  

1. Prerequisites

To be able to follow the instructions in this article, you need to have a:

• Working application instance with:
  • FBA customisations deployed
  • FBA users in the system
• Working knowledge of App Manager
• Configured App Manager instance
• Admin rights for your application server

2. Changing the authentication method

To change the authentication method:

1. Go to \wwwroot\[Pentana instance]\Client\XtraDeploy/
2. Rename vision.exe.config.xml to vision.exe.config.WIN.xml.
3. Rename vision.exe.config.FBA.xml to vision.exe.config.xml.
4. Open App Manager.
5. Select the correct instance
6. Navigate to the Setup tab.
7. Scroll down to the Client section.

8. Ensure that the Deployment Method reads ClickOnce.
9. Ensure that the Location is the path to your ClickOnce path
10. Go to Config.
11. Switch to the Client tab.
    You will see that this is now an unconfigured file
12. Click Replace Variables.
13. Switch to the Client tab again.
14. Click Save.

The log at the bottom of the display should read:

(Config) Replacing variables in web.config....
C:\inetpub\wwwroot\PreQA\Client\XtraDeploy\vision.exe.config.xml has been saved.
(Config) FileHashing XtraDeploy (C:\inetpub\wwwroot\PentanaUAT\Client\XtraDeploy)
(Config) FileHashing Completed 

If you do not see 'FileHashing Completed', save the Client tab again.

The next time a ClickOnce user launches the desktop application they should see the FBA login screen.

3. Deploying the configuration

If you are deploying the client via MSI or some other method:

1. Follow the steps above,
   This creates a new config file.
2. Go to \wwwroot\[Pentana instance]\Client\XtraDeploy.
   It should contains this new file.
3. Copy the file to your deployment package.
4. Change the file name from vision.exe.config.xml to vision.exe.config.
5. Deploy the update.