i think you are asking a few questions here, so i will try and repeat what i think the questions are, and then answer them
Question 1) is there a way to customize the login screen
Answer: not in beta 1, and not officially in V1. However, an unsupported for V1 (meaning it's not an officially supported scenario, and that we might break it completely in V2) scenario is using a custom login.aspx page when LS apps are configured
for Forms auth.
Question 2) is there a way to change the database connection string based on who is logged in?
Answer: No.
If your business requirements are that some people go to database A, and some people go to database B, those would need to be seperate deployments of the same LS application. users who should go to A should be given permission to applicaiton A, and
users who should go to B should be given permission to application B.
Infact, you could combine logic in the custom login page to decide which LS application to direct people to, and make it _seem_ like one big application.
Question 3) can LS filter data so only the right people can see it
Answer: Yes. LS has a users, roles, and permissions system. Users are placed into roles, and permissions are granted to roles. In an LS application, you define the names of the permissions at development time, and anywhere you can write
code, you can do permissions checks, such as
if (User.HasPermission(Permissions.CreateInvoice)) {
// create the invoice
}
You create LS users and Roles after the application is deployed. You then use the built-in administration screens to give the permissions you created earlier to the various ROles, and to put users in the appropriate roles.
One final thing i am concerned about: i am confused about the architecture of your app. Are different customers connecting to different databases, with different connection strings? Or are all the customers in in the same database, and should
only be able to see some of the data in that database?
