Bug #3207
Revamp signup process with enhanced security measures.
0%
Description
Currently there are few security breaches, fix it and enhanced security.
Replace the device while Signup or Login the user.
Impact Analysis
during Login and otp Registration
Related issues
Updated by Jithin Kuriakose over 1 year ago
- Related to Bug #3179: Register API Calls twice while Creating a Rider account using the iOS Application. added
Updated by Jithin Kuriakose over 1 year ago
- Milestone deleted (
Sprint 22 Tukxi Ride 2024 Aug 01 to Aug 31) - Milestone set to Sprint 21 Tukxi Ride 2024 July 01 to July 31
- Branch name set to sprint-21_shaheel_3207
Updated by shaheel Navas over 1 year ago
CREATE TABLE `ridedoot_mine`.`driver_rider_otp_verification` (
`iOtpVerifyId` INT NOT NULL AUTO_INCREMENT COMMENT ' ',
`vUserType` ENUM NULL,
`vVerificationId` VARCHAR NULL,
`vDeviceId` VARCHAR NULL,
`dCreatedAt` DATETIME NOT NULL DEFAULT now(),
PRIMARY KEY (`iOtpVerifyId`));
Updated by shaheel Navas over 1 year ago
ALTER TABLE `ridedoot_mine`.`driver_rider_otp_verification`
CHANGE COLUMN `iOtpVerifyId` `iVerifyId` INT NOT NULL AUTO_INCREMENT COMMENT ' ' ;
Updated by shaheel Navas over 1 year ago
Please ignore previous Query for Create
CREATE TABLE `device_otp_verification` (
`iVerifyId` int NOT NULL AUTO_INCREMENT COMMENT ' ',
`vUserType` enum('rider','passanger') DEFAULT NULL,
`vOtpVerificationId` varchar(100) DEFAULT NULL,
`vDeviceId` varchar(50) DEFAULT NULL,
`dCreatedAt` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (`iVerifyId`)
) ENGINE=InnoDB AUTO_INCREMENT=26 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
Updated by Jithin Kuriakose over 1 year ago
- Due date set to 08/15/2024
- Status changed from Resolved to QA Ready
Updated by Anupama P over 1 year ago
- Milestone deleted (
Sprint 21 Tukxi Ride 2024 July 01 to July 31) - Milestone set to Sprint 24 Tukxi Ride 2024 Oct 01 to Oct 31
Updated by Anupama P over 1 year ago
- Status changed from Resolved to QA Ready
- Target version changed from 1.0.4 to 1.0.6
Updated by Firosha Fathima over 1 year ago
- Status changed from QA Ready to Reopened
1, When the user logged in with one device,the same user logged in with the another device the previously logged device is not expiring(session out)
ER:when the user user logged in with the another device the previously logged device should session out
AR:Previously logged device is not getting expired.
2,In otp page, when we click on verify for the first time it will not redirected,only on the second click it navigates to the next page.
ER:It should navigate to the next page while clicking verify for the first time
AR:It is not navigated to the corresponding page.
Updated by shaheel Navas over 1 year ago
1, When the user logged in with one device,the same user logged in with the another device the previously logged device is not expiring(session out)
ER:when the user user logged in with the another device the previously logged device should session out
AR:Previously logged device is not getting expired.
2,In otp page, when we click on verify for the first time it will not redirected,only on the second click it navigates to the next page.
ER:It should navigate to the next page while clicking verify for the first time
AR:It is not navigated to the corresponding page. -Fixed
for Developer : change include 'assets/plugins/ckfinder/core/connector/php/vendor/autoload.php'; on common.php