NOTE : ( I WANT THE SOLUTION CODE TO BE IN C# CODING LANGUAGE. THIS IS AN ASP.NET WEB FORM WPRK). Most importantly I am much interested in the Code behind file on how all errors and validations are handle in various cases.

Page 7 of 24 . A User attempts to access a page that requires a user to be successfully logged in first o occurs when a user explicitly enters the URL of a re- stricted page without first authenticating Note that although customer registration is required, there is no admin or technician reg Login istration for the application, rather admins and technicians, only gain access, via an ex plicit entry inserted into the applications database. Such an insertion would typically be performed by the application development team during the initial deployment and setup The Business Analysts have provided a wireframe mockup of a potential login page below: To elaborate further, at configuration time, your site must recognize at least one valid ad min user, an admin user with the following credentials, username-admin@isp.net, pass- word-p@sswordl, and at least one valid technician, a technician user with the following credentials, username-tech@isp.net, password-p@ssword2 LOGIN Usename The system also needs to deal with the use case where a customer, has forgotten their credentials and thus requires some mechanism to either retrieve or reset their lost creden tials. The specification for this requirement (either retrieving a forgotten password or re- setting a password) is open to design and developer preference, again as long as the use case is dealt with within the solution. End of dooument Figure 7: Login Page The login page will prompt the user for the necessary credentials (username / password) to login. In summary, the page will allow the user to submit their credentials and thereafter login. The Login page will also be responsible for displaying error messages in the event of the following scenarios: Invalid username and/or password combination is provided o occurs when a user enters an invalid username/password combination. Login Error and Authentication A Web Poge http://localhost 8080/TechknowPro/logn aspx LOGIN ld username/password Invalid Username Logn Regster Figure 8: Login Error Authentication is primarily used for validating a forwarded username and password against a list of recognized users. This system expects two parameters (a username and password). If any mandatory parameters are missing, the application should direct the user back to the login page without displaying any error messages If the user authenticates successfully, the system should store the user's information in a session object and direct the user to the appropriate home page Alternatively, if the user fails authentication, the application should direct the user back to the login page with an useful error message, educating the user of the failure, similar to the wireframe provided (Login Error) Page 9 of 24 REGISTRATION PAGE Fstoe Cantem Pasond Registration A registered user is a recognized user who has previously registered to the application. Registered users are known users that have provided necessary profile information (First and last name, address, email, password, etc..) to prove their identity. The system allows users to register simply by clicking the register button on the login page. Naturally, your application must allow for the entry of registered user (customer) information, stored locally within the systems database Figure 9: Registration Page End of document Typical restrictions must follow, for example, a profile cannot be registered more than once, duplicate entries must be prohibited. For this application, a registration is deemed unique, simply by evaluating and comparing a customer profile's email address (case n sensitive), where email address and username are synonymous Registration Entry The Business Analysts have provided a wireframe mockup of a potential registration page below: Page 10 of 24 Your application should notify the user when their registration attempt is successful. The notification is performed in two steps. I. The user must be presented with notification confirming successful registration (see Sample Successful Registration) 2. The user must also receive a verification email sent to their corresponding email address. The content of the email must reference the users first and last name The content of the email must also provide a link to the login page of the web application. Figure 10: Invalid Registration Your application must validate all form data supplied to the registration page and edu- cate the user if a failure occurs. Treat all fields as mandatory fields. Please refer to the section entitled " Validation Requirements" for further details. As mentioned above, if a user supplies valid information for registration and the registra tion is successful (committed successfully to the database), your application is required to notify the user of the successful registration into the system Invalid Registration The Business Analysts have also provided a wireframe mockup of a potential invalid reg istration page below Figure Il: Sample Successful Registration nd of ducument Page 7 of 24 . A User attempts to access a page that requires a user to be successfully logged in first o occurs when a user explicitly enters the URL of a re- stricted page without first authenticating Note that although customer registration is required, there is no admin or technician reg Login istration for the application, rather admins and technicians, only gain access, via an ex plicit entry inserted into the applications database. Such an insertion would typically be performed by the application development team during the initial deployment and setup The Business Analysts have provided a wireframe mockup of a potential login page below: To elaborate further, at configuration time, your site must recognize at least one valid ad min user, an admin user with the following credentials, username-admin@isp.net, pass- word-p@sswordl, and at least one valid technician, a technician user with the following credentials, username-tech@isp.net, password-p@ssword2 LOGIN Usename The system also needs to deal with the use case where a customer, has forgotten their credentials and thus requires some mechanism to either retrieve or reset their lost creden tials. The specification for this requirement (either retrieving a forgotten password or re- setting a password) is open to design and developer preference, again as long as the use case is dealt with within the solution. End of dooument Figure 7: Login Page The login page will prompt the user for the necessary credentials (username / password) to login. In summary, the page will allow the user to submit their credentials and thereafter login. The Login page will also be responsible for displaying error messages in the event of the following scenarios: Invalid username and/or password combination is provided o occurs when a user enters an invalid username/password combination. Login Error and Authentication A Web Poge http://localhost 8080/TechknowPro/logn aspx LOGIN ld username/password Invalid Username Logn Regster Figure 8: Login Error Authentication is primarily used for validating a forwarded username and password against a list of recognized users. This system expects two parameters (a username and password). If any mandatory parameters are missing, the application should direct the user back to the login page without displaying any error messages If the user authenticates successfully, the system should store the user's information in a session object and direct the user to the appropriate home page Alternatively, if the user fails authentication, the application should direct the user back to the login page with an useful error message, educating the user of the failure, similar to the wireframe provided (Login Error) Page 9 of 24 REGISTRATION PAGE Fstoe Cantem Pasond Registration A registered user is a recognized user who has previously registered to the application. Registered users are known users that have provided necessary profile information (First and last name, address, email, password, etc..) to prove their identity. The system allows users to register simply by clicking the register button on the login page. Naturally, your application must allow for the entry of registered user (customer) information, stored locally within the systems database Figure 9: Registration Page End of document Typical restrictions must follow, for example, a profile cannot be registered more than once, duplicate entries must be prohibited. For this application, a registration is deemed unique, simply by evaluating and comparing a customer profile's email address (case n sensitive), where email address and username are synonymous Registration Entry The Business Analysts have provided a wireframe mockup of a potential registration page below: Page 10 of 24 Your application should notify the user when their registration attempt is successful. The notification is performed in two steps. I. The user must be presented with notification confirming successful registration (see Sample Successful Registration) 2. The user must also receive a verification email sent to their corresponding email address. The content of the email must reference the users first and last name The content of the email must also provide a link to the login page of the web application. Figure 10: Invalid Registration Your application must validate all form data supplied to the registration page and edu- cate the user if a failure occurs. Treat all fields as mandatory fields. Please refer to the section entitled " Validation Requirements" for further details. As mentioned above, if a user supplies valid information for registration and the registra tion is successful (committed successfully to the database), your application is required to notify the user of the successful registration into the system Invalid Registration The Business Analysts have also provided a wireframe mockup of a potential invalid reg istration page below Figure Il: Sample Successful Registration nd of ducument