In an existing C#.net 2008 desktop application, my company wants me to add active directory to the application. To accomplish this task, I was thinking of accomplishing this task in one of three maners. I am wondering if you can tell me which method is better and why. Also if you have another suggestion, can you tell me what the better method would be. Here are my options:
1. I could have the users click on a shortcut to the exe to get the application started. By using windows authenication, the application would know who the user is. If the user does not have the access, the user would be taken out of the exe with a popup saying 'they do not have access to the to this application and they should contact the 'administrator'.
2. The user can enter their user name and credentials in a logon screen. If the user does not have access to the application, the user would be redirected to a popup saying 'they do not have access to the to this application and they should contact the 'administrator'.
3. The user can open on the C#.net 2008 desktop application and click on the part of the desktop they want to run. By using windows autehnication and/or active directory the application will be determine if the user has the access to run a certain feature of the application. If they do not have the access, the user redirected to a popup saying 'they do not have access to the to this application and they should contact the 'administrator'.
Satish BhatPosted Aug 22, 2011, 1:18 AM
Now there are 2 departments in your client's organization (Purchase & Accounts). Your client does not want accounts dept. to access Purchase module and purchase dept. to access accounts module. Now one of the options for you to create a single application and based on the user's role, enable/disable access to sections of your application.
jasminiePosted Aug 20, 2011, 5:42 PM
Why would method 3 require role based? How is that way setup for role based?
Satish BhatPosted Aug 20, 2011, 3:45 AM
i.e
Users click on a shortcut to the exe to get the application started. By using windows authenication, the application checks the the user credential. If the user does not have the access, a popup of login form with a message saying 'They do not have the access to this application and whether they wish to login as a different user".
In point 2 you have one issue that user has to login always to enter the application. By adopting the above procedure, you can eliminates this issue.
Note: If your application is very critical and requires good security measure, I would suggest method 2. Because, if a user keeps his computer without locking and goes out for a break, then anyone can use the application and make critical changes.
If there are roles, then method 3 is the suggested choice.
Jiteendra SampathiraoPosted Aug 20, 2011, 1:01 AM
To my knowledge those all 3 are very good...But 2 point is the most preferred choice among these three.....
and 3 is also fine....