| Subject: | Barcode end marker functionality review |
| Summary: | The current system design has the configuration for "barcode_end_mark" which is used in login and product scan. The barcode report does not use "barcode_end_mark" The login functionality behaves differently when the enter key is press and end marker exists. Change request: - We need to agree if the barcode end mark should be used to initiate the enter key. How does this affect barcode product report?
- User security code functionality no longer works. We need to agree on how security code works.
Justification: - The barcode end mark was introduced for scanners that do not press the enter key. Is this still required?
- We need to make barcode functionality consistent so it can be easily understood
Suggested Design: - Remove functionality of scanning username + password as this is a high-security risk. Users can still manually type username and password to allow price change, etc.
- The security code scan should consist of barcode start mark + security code + barcode end mark
- When the start and end mark is identified, the application should XXXXXct the security code and verify.
- Add functionality to generate security code when a user is created.
- Security code should be complex
- Removed security scan where username and password is used
- Change the user barcode report to handle changes above
- barcode end mark should be used to initiate the enter key
|
| Audit Notes: | |
| 27 Nov 2017 | 09:22AM Comment 1 by Alvis (Link Technologies) Case 8946 added to project 8.2 |
| 05 Dec 2017 | 04:12PM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 05-12-2017 04:12 PM Time Taken: 8.00 |
| The following changes have been made: - When we have the "Password start mark" and "Password end mark" matching, we perform automatic login
- Content between markers can be:
- Username.Password
- Security code
- If the separator is present, we have the Username and Password
- If we have the security code, we get the username and password from the database and sign the user in
- User authorization has been changed to use the same mechanism
- If we find multiple users with the same security code, we log a message and do not authorize the user
Regards
Sanjay/Alvis |
|
| 06 Dec 2017 | 01:19PM Comment 3 by Sanjeet (Link Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 06-12-2017 01:19 PM Time Taken: 1.00 |
| QA for product and Patch Releases Step 1 - Developer to system test changes until not issues are found Step 2 - Product expert to complete Product QA. Test Summary
Table 1 - Summarised list of issues | No | Issue Description | Resolved? | 1 | User ID + Password with Start and End Marker as "PWD" | Passed | 2 | Security ID with Start and End Marker as "PWD" | Fail- "User Login Information is Invalid | 3 | | | 4 |
|
| 5 | | |
QA Environment Details
Notes:
|
|
| 06 Dec 2017 | 01:34PM Comment 4 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 06-12-2017 01:34 PM Time Taken: 1.00 |
| Changed the user barcode report to add login start and end mark to security code. |
|
| 08 Dec 2017 | 09:04AM Comment 5 by Sanjeet (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 08-12-2017 09:04 AM Time Taken: 1.00 |
| QA for product and Patch Releases Step 1 - Developer to system test changes until not issues are found Step 2 - Product expert to complete Product QA. Test Summary Table 1 - Summarised list of issues | No | Issue Description | Resolved? | 1 | Barcode - User/Password | Pass | 2 | Barcode - Security | Pass | 3 | | | 4 |
|
| 5 | | |
QA Environment Details
Notes:
|
|
| 24 Jan 2018 | 03:51PM Comment 6 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 24-01-2018 03:51 PM Time Taken: 1.00 |
| Documentation updated on the case Documentation updated under - POS--> Technical Reference --> POS Configuration.
- Systems Manager --> User Login
- Systems Manager --> Reports --> User Login Barcode
|
|
| 09 Oct 2019 | 08:14AM Comment 7 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019 |