CIS 407 iLab 6 of 7: Login and Security Levels

Title: CIS 407 iLab 6 of 7: Login and Security Levels

Type: Instant Download

Format: Zip Folder (Contains all the files needed for accurate tutorial)

Version: Current 2013-14 (Click on tutorial image to view snapshot)

Frequently Asked Questions

What is included in the full course package? The entire course study guide includes the homework solution in zip file for CIS 407 Lab 6: Login and Security Levels (bachelors program)

Your tutorial will include these files:

• CIS407_Lab6.Zip

What if I find a question is missing? Just shoot us an email or contact us via live chat. Our expert DBM tutors will add the answers to the study guide within 1 to 3 days. You will receive a free update to the study guide with the answers you need.

Will this help me with CIS 407 problems? Yes, this guide is designed to help students get through the CIS 407 Lab 6 exercise with ease.

CIS 407 iLab 6 of 7: Login and Security Levels

1. Open Microsoft Visual Studio.NET 2008.
2. Click the ASP.NET website named PayrollSystem to open it.
3. Create a new web form named frmLogin.
4. Drop a login control onto the form. 
5. Set the properties of the login control as follows:

1. Add the cool productions logo to the frmLogin form. Do not hylerlink the logo.
2. Highlight everything in the form, then click Format, Justify, Center. Save your work.
3. Go to the Solution Explorer, right-click on frmLogin, and left-click on Set As Start Page. Then run the website to check if the web form appears correctly.

1. Create a new DataSet called dsUser. Use the table tblLogin as the database table for this dataset. Do this in the same way you added datasets in the previous labs. 
2. Open the clsDataLayer and add the following function:

1. Double-click on the login control you added. Add the following code to the login control Authenticate event handler:

1. Open the frmPersonnel form and add the following code to its Page_Load() function:

1. Set the start page as frmLogin.aspx. Run the website. Try to log in with both User Name = Mickey and Password = Mouse and User Name = Minnie and Password = Mouse. Any other user ID and password should not allow you to log in.
2. When the user logs in we want to restrict what they can see and do based on their user role. The role is stored in the database table tblUserLogin. Mickey Mouse has all privileges whereas Minnie Mouse has read only privileges. We want to control the visibility of the links on the frmMain page.
3. Initially we did not set the ID of any of the Link Button or Image Button controls that we used on frmMain. In order to make our code more maintainable we will change the IDs as follows:

1. Modify the main form so that the following options are turned off for nonadmin users: 
• Add New Employee
• View User Activity
• Edit Employees
2. You now have a web application that honors the role of the logged in user. We don't have a way of managing the user roles and users in the system.
3. Add a new form called frmManageUsers that will allow the user to add new users. The user will also need to be able to view all users and modify or delete any of the users in the database. Add a main form option called Manage Users that is only accessible to admin users. Add the link and image buttons as we have done in the past. Add the CoolBiz logo that is hyperlinked as you did in previous assignments.
• For the security level of the user, use a dropdown list control to allow the user to select from A or U.
• Name the controls with names that make sense.
• Add code as appropriate to the code behind and clsDataLayer.
4. Hints:
• Make sure you reestablish your database connection if you copied the files from a previous lab.
• Update any DataSource controls you added with the new Payroll database location.
• You can turn a control on or off by setting it's Visible property.
• You can add a data entry form for new users and a grid displaying all users all on the same form.
• To force a gridView to refresh call its DataBind method.
• In order to use the Advanced SQL Generation option (allowing you to update/delete records) there must be a primary key defined on the table you are generating SQL for. tblUserLogin needs to have a primary key set on the UserID column. You can do this in Access.
5. Test your application to make sure you are logging in with an invalid user id. Try to log in with both Minnie and Mickey and make sure the UI adjusts by the role properly. Make sure you can utilize the Manage Users functionality to add/modify/delete and view user information. Once you have verified that everything works, save your project, zip up all files, and submit in the Dropbox.