Here's the background: we've had a web app online for a few months that has now attracted a number of user accounts. We now have a sister application that we'd like to put online under a separate subdomain. We don't want our existing users to have to create a new set of login credentials for the new app - we'd like them to be able to log in with the same username (and possibly password) as the first app.
My first step was to set up a dedicated security database using aspnet_regsql, and copy the existing membership data from the first app into this database. I then point both applications at the same security database by configuring the membership provider in the web.config of each app.
First problem: I have to set the provider in both applications to point to the application name of the first application. While this allows users of the first app to log straight into the 2nd app without any further steps, it seems wrong to set both providers as t ...
Go to the complete details ...