Using the latest Community Kit from CodePlex, install and configure single SharePoint WSS 3.0 server to use Forms Authentication. Initially, a single development site will be used as the testbed. The solution must work with the existing coded environment. The contractor must prepare to reverse (unwind) the installation should that be required.
The goal is to have a single “membership” screen/logon whereby a user can authenticate via their own email address and password or via an Active Directory entry. FBA-based users should be able to create, recover, or reset logon passwords and credentials. The “membership” screen should function only when a logon is required or requested by the user. It should not automatically be required when a site accepts anonymous access.
The current target site collection has several permission groups. Each cloned site collection will look similar in nature. Thus, there will always be a group of administrators, basic users, directors, management/leadership, and operations at a minimum. The taxonomy may change depending on the client application. Setup roles within the FBA environment if the roles will help automate the process of assigning or providing the appropriate rights to a user.
Using the Community Kit, ideally when a new or change requests populates the list, an administrator or someone will receive an alert to appropriately complete the request by making whatever group assignments or other approvals that are required.
When creating the “membership” page/form, make sure that the UI can be completely adjusted within the Site Collection Theme. Use “class” callouts whenever possible. The contractor may use the web parts provided within the Community Kit if these web parts provide acceptable UI and functionality.