How to design intranet to have individual .Net modules

canuckconsulting
canuckconsulting used Ask the Experts™
on
We have a number of  mvc.net internal applications we want to consolidate into our intranet and are not sure the best approach is for this.  

We expect create an MVC Intranet app which would display all applications the logged on user has access to based on their AD credentials.  So for example, a Customer Services user would have access to the Order Entry, Product Details, and Customer History applications

What we are unsure of is how to seamlessly transition to that application such that the user does not have to log in again.  Instinctively we see value in keeping the applications as separate MVC projects that we can update without changing the intranet app itself.

I realize this is not a concise question but we are struggling a bit here to state our situation clearly..
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Senior Software Engineer
Top Expert 2009
Commented:
If all are Intranet applications then windows authentications will suffice to do the job.
Windows authentications does not require the user to log in again and you can use roles (user groups) to determine who has access to a particular app or better you can customize the home page to display to the user only the apps they have access to.
In that sense you can keep all applications as separate MVC projects as there is no need to modify except for the role permissions, then you can create a main website application as the main entry to your corporate apps.

Author

Commented:
Thanks.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial