I've search the web for information about having a single user be authenticated across multiple applications. The bulk of what I've found has been just that. However, I don't want any specific user (except my superuser) to be able to get into every application.
I'm developing a website for my company that currently uses ASP.NET authentication tables (local tables) for user authentication. Originally, the website was designed to be a single site that would support multiple clients (our customers), and be able to
separate one client's data from the other. Unfortunately, some clients wanted their data physically separate and the site "branded". So, we decided to provide separate sites, each with their own local ASP.NET tables.
There is a "master" database that each of these sites communicate with. The master happens to be on the same server as all of the other local app databases. The master contains copies of some data elements from the local ap ...
Go to the complete details ...