| Subject: | Unable to log into Backoffice with new users created in LinkWeb - Version 9.5 |
| Summary: | 1. Explain the issue Unable to log into Backoffice with new users created in LinkWeb - Version 9.5 2. Steps to reproduce - Create a new user in LINKWEB. Global Administration -- Create New User.
- Reset the password for the user.
- Navigate to Backoffice.
- Try logging into Backoffice with the password emailed at reset. Login Fails. Refer to Figure 1.
- In Linkweb, assign the user administrator role and change password to 66666.
- Try logging into Backoffice. Login Fails. Refer to Figure 1.
- Map the user on 222.
- Try log into Backoffice. Login Fails. Refer to Figure 1.
3. Environment Details- Version 9.5 Alpha 1
- Database - LINKSOFT-UAT95-LINKFJ
- Server - QA4
- Setup - Demo
- User - Simran
4. Screenshot: Include screenshots for cases that need clarity. Reduce the image size before attaching it to the case. Figure 1: Unable to log into Backoffice. 
Thanks
Rashna |
| Audit Notes: | Edited by sanjay on 05/03/19 09:40. Edited by rashna on 16/08/18 13:41. |
| 16 Aug 2018 | 04:05PM Comment 1 by Alvis (Link Technologies) Case 9517 added to project 09.5 |
| 17 Aug 2018 | 09:28AM Comment 2 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 17-08-2018 09:28 AM Time Taken: 1.00 Notes: Edited by rashna on 17/08/18 09:44. |
| As per the gtm meeting with Alvis. This issue is caused because password in web is encrypted. We removed the portion "passwordFormat= Encrypted" from the web config file for " AspNetSqlMembershipProvider" section. User was then able to log in. Please address the above. Thanks
Rashna and Alvis. |
|
| 21 Aug 2018 | 06:11PM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 21-08-2018 06:11 PM Time Taken: 2.00 |
| Development work for this case has been completed. The change will be available in version: 95 1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Changed password format to Hashed. Passwords are encrypted one-way using the SHA1 hashing algorithm.
2. The issue was caused by: - PowerBuilder cannot handle com objects that utilize the Machine Key Element
3. Next Step - UAT
|
|
| 23 Aug 2018 | 08:01AM Comment 4 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 23-08-2018 08:01 AM |
| Proceed with UAT using LinkSOFT95BETA2 For documentation - please state that “Encrypted” is less secure and is not supported by Link Technologies |
|
| 24 Aug 2018 | 10:29AM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 24-08-2018 10:29 AM Time Taken: 1.00 |
| Hi Sanjay
QA Results Tests carried out according to requirements specified on the case header Test Results Summary Table 1 - Summarised list of issues | No | Test Description | Pass/Fail | 1 | Create a new user in web as Sam. User is created as approved | Pass | | 2 | Log into Backoffice. | This is not allowed system prompts security message.Refer to Figure 1. Modify the message to give a clear message to the users. | | 3 | Map the user created in 1 above on 222. User should be able to login | Pass |
Figure 1: Message
Environment Details - OS version:Windows Server 2012
- Application version:9.5 Beta 2
- Setup: Demo
- Server : QA4
- Database:LINKSOFT-UAT95-LINKFJ
Steps to reproduce failed scenarios: - N/A
Next Step:
Sanjay to modify the message for clarity |
|
| 30 Aug 2018 | 06:34PM Comment 6 by Sanjay (Link Technologies) Assigned To: Alvis (Link Technologies) Followup Date: 30-08-2018 06:34 PM Time Taken: 2.00 |
| Hi Alvis, I have checked the API, the result of an Invalid Username and password is: "Invalid username/password" Can we look at how this is reflected in the API call from Powerbuilder? |
|
| 03 Sep 2018 | 04:54PM Comment 7 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 03-09-2018 04:54 PM |
| Could not reproduce the issue. The system is displaying the message "Incorrect Username/Password" if the user is not approved. Please retry in beta 3. |
|
| 10 Sep 2018 | 09:04AM Comment 8 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 10-09-2018 09:04 AM Time Taken: 1.00 |
| System test completed. proceed with UAT. |
|
| 20 Sep 2018 | 03:09PM Comment 9 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 20-09-2018 03:09 PM Time Taken: 1.00 |
| Hi Sanjay
QA Results Tests carried out according to requirements specified on the case header Test Results Summary Table 1 - Summarised list of issues | No | Test Description | Pass/Fail | 1 | Create a user as "James" in Linkweb. Map the user on 222. The user should be able to log into Linkweb and BO | Pass | 2 | Sign Up a user account as "Tina". The user should be able to log into Linkweb | Pass |
Environment Details - OS version: Windows Server 2012
- Application version: 10 BETA 3
- Setup: Demo
- Server : 10.0.0.10
- Database: LINKSOFT-DEMO-10-RASHNA
Steps to reproduce failed scenarios: N/A Next Step: Case assigned to Sanjay for closure.
|
|
| 21 Sep 2018 | 01:58PM Comment 10 by Alvis (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 21-09-2018 01:58 PM |
| Thanks Rashna |
|
| 09 Oct 2019 | 08:14AM Comment 11 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 |