This FAQ assumes we'll be moving the Passwordstate database & web site to different servers

• Install Passwordstate on your web server (don’t run through the initial setup wizard that you would normally do for a new installation)
• Move the database to your production server (refer to your SQL Server documentation for how to do this)
• Edit the '/setup/scripts/create_sql_account_v4.1.sql' file to specify the [SQLLOGINNAME] and [PASSWORD] you would like to use (ensure the [ ]'s are removed)
• Execute the script '/setup/scripts/create_sql_account_v4.1.sql' against the appropriate database server
• Edit the 'PasswordstateConnectionString' element in 'web.config' file, specifying appropriate values for [SERVERNAME], [SQLLOGINNAME] & [PASSWORD] (ensure the [ ]'s are removed)
• Edit the 'SetupStage' element in 'web.config' file, change the value to 'Setup Complete'
• Modify the cname DNS entry you created to point your browsers to the web server application.

This FAQ assumes we'll be restoring both the Passwordstate database & web site.

• Ensure the following are backed up:
• Passwordstate4 database
• /web.config & /setup/scripts/create_sql_account_v4.1.sql
• Restore database (refer to your SQL Server documentation for how to do this)
• Reinstall Passwordstate on your web server (don’t run through the initial setup wizard that you would normally do for a new installation)
• Restore the 'web.config' & 'create_sql_account_v.4.1.sql' mentioned above
• If the host name of the SQL server or web server has changed, you’ll need to edit the 'PasswordstateConnectionString' element in 'web.config file', specifying appropriate values for [SERVERNAME], [SQLLOGINNAME] & [PASSWORD] (ensure the [ ]'s are removed)
• Execute the ‘create_sql_account_v4.1.sql’ script against the appropriate database server
• If your web server IP address has changed, you may need to modify the DNS cname entry you’ve created to point your browsers to the Passwordstate web site.

The most common cause of this type of error is ASP.NET web service extension not being enabled. To do this, follow these steps:

• Start Internet Information Services Manager (IIS)
• Browse to 'Web Service Extensions', and Allow 'ASP.NET' web service extension
• Restart IIS

The most common causes for this type of error are:

• The server doesn't belong to the Active Directory domain your account does - they need to be on the same domain
• The URL you're using to access Passwordstate has an underscore in it i.e. Passwordstate_4
• Problem occurs when trying to browse the Passwordstate web site on the Windows Server itself - this article may explain why - http://support.microsoft.com/kb/896861. Try browsing from a desktop computer to see if the problem persists.

A key development goal for Passwordstate version 4 was ensure the integrity and confidentiality of sensative data. This is achieved by 256bit AES encryption within the database, and code obfuscation in a .NET Assembly protecting encryption/decryption functionality.

Because of this design, no longer can Database Administrators grant themselves access to unauthorised data via the backend database, or Web Administrators write their own ASP.NET code to try and retrieve data.

It is highly recommended that 'Security Administrators' select the option 'Password Protect Administration Area' under System Settings, as this will also mitigate against System Administrators logging onto the network with their account, and giving themselves access to the 'Administration' area.

As outlined in the FAQ item 'How secure is Passwordstate', Database Administrators cannot gain access to unauthorised data even if they have access to the SQL Account details. So no, it is not necassary to encrypt this database connection string.

It is recommended to use an SSL Certificate with Passwordstate to encrypt the data being passed back to the browser.

There are 3 different methods you can use to add users to Passwordstate.

• Manually adding them - specifying all fields manually
• Importing from Active Directory
• Import from a CSV file - You may want to export user details from Active Directory into a CSV file, the import into Passwordstate (the Import option provides you with detail for the format the CSV is required to be in)

Yes, grid views in Passwordstate can be customised per user. The following customisation are available:

• Number of rows
• Column ordering
• Column sorting

Note: It's important the user clicks on the 'Save Grid Layout' link to ensure the changes are saved for them.

Yes, individual users can choose not to be notified of changes to shared passwords under the 'preferences' section.

Yes, individual users can choose not to be notified of expiring passwords under the 'preferences' section.

Yes, Passwordstate supports multiple Active Directory domains & Forests.

In order for Passwordstate to work across domains, you must have the appropriate DNS forwarders configured, and domain trusts in place. For the instructions given below, we will assume the following domain structures:

• DomainA (domaina.clickstudios.com.au) is hosting the Passwordstate4 web site
• DomainB (domainb.clickstudios.com.au) - Users belonging to DomainB wish to access Passwordstate in DomainA

Configure Passwordstate Web Site

• For the Passwordstate web site, add a fully qualified Host Name entry to the 'Site Bindings' i.e. passwordstate4.domaina.clickstudios.com.au

Configure Browser Settings

• On DomainB, add the fully qualified host name 'passwordstate4.domaina.clickstudios.com.au' to the list of sites for the security zone 'Local intranet' in your browser - this is required so your authentication details are passed through to the Passwordstate web site
• When browsing to the passwordstate4 web site in DomainB, use the fully qualified name

Querying Users in Active Directory Across Domains

When importing users via Active Directory, you will need to specify the appropiate LDAP querystring for the domain in question i.e.

• Go to 'System Settings'
• For the field 'Domain Name', specify DC=domaina,DC=clickstudios,DC=com,DC=au to query users in DomainA
• For the field 'Domain Name', specify DC=domainb,DC=clickstudios,DC=com,DC=au to query users in DomainB

Yes, Passwordstate works with Microsoft's SQL Server Express Edition, and can be found at - http://www.microsoft.com/express/sql/default.aspx

To view information about Role-Based Access Control within Passwordstate, please visit the Passwordstate features page - Passwordstate Features

To view information about audit events within Passwordstate, please visit Passwordstate Audit Events