A due by midnight, Sunday, January 10 (3-6 written pages, APA Format): Outline t
ID: 3661574 • Letter: A
Question
A due by midnight, Sunday, January 10 (3-6 written pages, APA Format): Outline the design of an authentication scheme that "learns." The authentication scheme would start with certain primitive information about a user, such as name and password. As the use of the computing system continued, the authentication system would gather such information as commonly used programming languages; dates, times, and lengths of computing sessions; and use of distinctive resources. The authentication challenges would become more individualized as the system learned more information about the user. Your design should include a list of many pieces of information about a user that the system could collect. It is permissible for the system to ask an authenticated user for certain additional information, such as a favorite book, to use in subsequent challenges. Your design should also consider the problem of presenting and validating these challenges: Does the would-be user answer a true-false or a multiple-choice question? Does the system interpret natural language prose? (3-6 pages, APA format)Explanation / Answer
User Authentication Use Case ID Req. ID: RID-001 Title: User Authentication Description: Users should be able to login to the system and view the home page. Actors: users Functional Flow 1. Login Name, password and Language (dropdown) should be displayed in login page. 2. User shall be authenticated with valid User Name and Password. 3. Inactive users should not able to Login to the application. 4. Post login screen contents will be displayed based on the selected language. 5. All the links based their privileges will be displayed in login home screen. 6. There should logout button in header of the all the pages. 7. If user clicks on the logout button, the session should be invalidated and login screen should be displayed. Business Rules 1. Password shall be masked while entering anywhere in the application 2. When Login first time User shall be navigated to Change Password screen, User need to key in the New Password, Confirm Password. 3. Login history shall be captured on each time when User successfully Logs into the application. Exception Flow: If the admin/user enters wrong password, Greater than configured number of times (invalid login attempts) then user account should be locked. Pre-conditions: 1. User should be active with valid login name and password. 2. The default user types should be available in the system through factory settings. Post conditions: 1. User should be able to successfully login into the system, after authentication. Alternative Flows If there are any errors during this process, the respective error message should be displayed. Sub Requirements N/A Field Name Mandatory Type Data Type Special Chars Length Login Name Yes Text Field AN . (Dot) and _ (Underscore) ‘@’ 20 Password Yes Text Field AN !@#$%^&* 20 Language Yes Dropdown NA NA NA 1.1 Validation and error messages Field Validation Error Message Blank <FieldName> cannot be empty Invalid Please enter data in valid format for <FieldName> Non-numeric <FieldName> should contain only numeric Length <FieldName> Length must be between <Min Length> and <Max Length> Incorrect / Invalid Password. Password is invalid, please enter valid Password With LOCKED status Your account is LOCKED, please contact Administrator with BLOCKED status Your account is BLOCKED, please contact Administrator With TERMINATED status Your account is TERMINATED, please contact Administrator User Id does not exists User ID does not exists
Most applications need to know the identity of a user. Knowing a user's identity allows an app to provide a customized experience and grant them permissions to access their data. The process of proving a user's identity is called authentication. Firebase provides a full set of authentication options out-of-the-box. When a user authenticates to a Firebase app, three things happen: Information about the user is returned in callbacks on the client device. This allows you to customize your app's user experience for that specific user. The user information returned contains a uid (a unique ID), which is guaranteed to be distinct across all providers, and to never change for a specific authenticated user. The value of the auth variable in your app's Security and Firebase Rules becomes defined. This variable is null for unauthenticated users, but for authenticated users it is an object containing the user's unique (auth.uid) and potentially other data about the user. This allows you to securely control data access on a per-user basis. Once a user authenticates to your app, Firebase manages their session, ensuring that the user is remembered across browser or application restarts. Firebase apps have built-in support for logging in with email & password, social login providers such as Facebook, Google, Twitter, and GitHub, and single-session anonymous login. Apps that use Firebase's built-in auth services can handle user login entirely with client-side code, saving you time and the headache of operating your own backend. If you have existing server-side authentication or single sign-on, you can also easily integrate it with Firebase. Download one of our helper libraries to generate authentication tokens on your own servers.
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.