R
Roel Korsten
Hello,
We're about to develop an ASP.NET 2.0 application. We're investigating all
the new stuff in ASP.NET 2.0 and how to use it.
There are 2 important specs for the app:
1. App has to have its own membership (login-page and so on) but when the
app is running in an Active Directory (AD) environment, the users should
login automatically (single sign-on) based on their Windows account
credentials. We want to use the membership controls of VS2005 but are they
flexible enough if the app is running in an AD environment?
2. Different users have different roles (multiple roles per user). Per rol
there are different functions for different controls (textboxes read-only,
gridviews that allow editing but not allow users to add records, checkboxes
invisible, and so on). When half of all possible controls on one page are
invisible in one role, the other controls need to be rendered on other
locations on the page ('blank spaces' not allowed). So the pages have to be
as generic as possible.
Is there a 'best way' to build such an application that meets this specs?
Any help appreciated.
Greetings,
Roel Korsten
We're about to develop an ASP.NET 2.0 application. We're investigating all
the new stuff in ASP.NET 2.0 and how to use it.
There are 2 important specs for the app:
1. App has to have its own membership (login-page and so on) but when the
app is running in an Active Directory (AD) environment, the users should
login automatically (single sign-on) based on their Windows account
credentials. We want to use the membership controls of VS2005 but are they
flexible enough if the app is running in an AD environment?
2. Different users have different roles (multiple roles per user). Per rol
there are different functions for different controls (textboxes read-only,
gridviews that allow editing but not allow users to add records, checkboxes
invisible, and so on). When half of all possible controls on one page are
invisible in one role, the other controls need to be rendered on other
locations on the page ('blank spaces' not allowed). So the pages have to be
as generic as possible.
Is there a 'best way' to build such an application that meets this specs?
Any help appreciated.
Greetings,
Roel Korsten