Hi ,

Please find Details for this change request,

New Request : Minimize session out time by 15 Min.

Current Implementation : Current Session out time is 20 Min , If any User Idle for 20 Min , Stay Sign in pop up message is shown. if no action perform (Stay Sign In or Cancel), After 2 min Its close down the application or network sessions is used.

New Implementation : With the new implementation , We just reduced the session time from 20 Min to 15 min.

Impacted Area : Session time out for all user reduced by 5 Min. So New session out time is set to 15 Min.

Affected File :

• \Web\Web Projects\Web.config.

Jaideep Vinchurkar Please have a review.

Thanks !

Verified on LB.
One issue found. Logged same issue as WT-11053.But this is Low priority issue because surviving spouse not most commonly used.
please refer checklist
WT-10727_Testcases.xls
Ready for stage.

CC: Rakesh Roy Hrishikesh Deshpande Sachin Hingole Prasad Pise

Thanks,
Sanjana Jadhav.

changing production due date as this deployed on stage today.

CC: Rakesh Roy Hrishikesh Deshpande Sachin Hingole Prasad Pise

Thanks,
Sanjana Jadhav

Hi Bhushan Patil

Verified on LB for Web application. Please refer attached test cases for multiple login functionality.
Request you to resume the execution for Mobile applications on LB.

CC: Rakesh Roy Hrishikesh Deshpande Prasad Pise Sachin Hingole Sayali Doshi

Thanks,
Sanjana Jadhav.

Hi Sanjana Jadhav,
Verified on LB for mobile - Android and iOS for Phone and Tablet
It is working as expected.
Hence assigning back to you again to move this ticket further process.
Cc: Bhushan Patil Sayali Doshi
Thanks,
Rohan Dhamorikar

Hi Sanjana Jadhav ,

This issues is already deployed on stage , please verify once.

Thanks !

Verified on Stage for Web Application
Browser - Chrome, IE 10, Firefox
Verified for below login :
1)Partner Login
2)Admin login
3)Broker login
4)Employee login
5)Default login
6)Surviving spouse login
Verified session logout and continue pop-up message and also verified multiple login scenario.
Working properly

Rohan Dhamorikar, Request you to resume testing for Mobile application on stage

CC: Hrishikesh Deshpande Rakesh Roy Prasad Pise Sachin Hingole Sayali Doshi

Thanks,
Sanjana Jadhav

Hi All ,

Doing code check into UI Refresh branch so item state may be get changed. Please proceed with last item state as well please verify on UIRefresh.

Thanks !

CC ::Jaideep Vinchurkar

Hi,

This ticket need not to be tested for mobile side. MOB-2645 ticket is created for mobile side.

Sanjana Jadhav, Request you to resume testing for further process.

CC: Bhushan Patil Sayali Doshi

Verified on azure using SA, Partner and broker login
Verified on production using partner login.
Testing In progress.

CC: Rakesh Roy Hrishikesh Deshpande Sachin Hingole Prasad Pise

Thanks,
Sanjana Jadhav.

Hi Vishal Bajad

Verified on Azure for Web Application
Browser - Chrome,Firefox

Verified for below login :
1)Partner Login
2)Admin login
3)Broker login
4)Employee login
5)Default login
6)Surviving spouse login

Verified session logout and continue pop-up message and also verified multiple login scenario.
Observe some issues NF-4453 (Old session is not not terminated) and WT-11053(Not able to login by surviving spouse after closing browser)

CC: Rakesh Roy Hrishikesh Deshpande Prasad Pise Sachin Hingole

Thanks,
Sanjana Jadhav.

Hi Vishal Bajad

Verified on Production for Web Application
Browser - Chrome,Firefox

Verified for below login :
1)Partner Login
2)Admin login
3)Broker login
4)Employee login
5)Default login
6)Surviving spouse login

Verified session logout and continue pop-up message and also verified multiple login scenario.
Observe some issues WT-10971 (Old session is not not terminated) and WT-11053(Not able to login by surviving spouse after closing browser)
Hence reopening this issue.

CC: Rakesh Roy Hrishikesh Deshpande Prasad Pise Sachin Hingole

Thanks,
Sanjana Jadhav.

As per discussion with vishal and prasad, issues found NF-4453 , WT-11053 and WT-10971 is not related to this jira. Hence unlink those link from this jira and assigned to respective developer, because this jira is only related to session timeout.
Session timeout working properly for all logins.Verified for all below login:
1)Partner Login
2)Admin login
3)Broker login
4)Employee login
5)Default login
6)Surviving spouse login
Working properly.Hence closing this jira.

CC: Rakesh Roy Prasad Pise Hrishikesh Deshpande Sachin Hingole

Thanks,
Sanjana jadhav

Hi All ,

As per client request , We hare reverted this changes from production. we have reverted session idle time from 15 to 20 minutes. now idle time for session is 20 min.

Sanjana Jadhav Please verify on production.

Thanks !

CC : Jaideep Vinchurkar Satya Samir Gaurav Sodani

Hi Vishal Bajad

Verified on production.
Session timeout popup comes after 20 min and after 2 min session logout.
Verified for following Login:
1.Partner
2.Broker
3.Admin
4.Employee
5.Default employee
6.Surviving spouse

also verified multiple login scenario. Verified on chrome, Mozilla firefox and IE 10 Browser.
Working properly.

PFA,

CC: Rakesh Roy Prasad Pise Hrishikesh Deshpande Sachin Hingole Satya Samir

Thanks,
Sanjana Jadhav