115,558 members

Skip to content. | Skip to navigation

Forums

General discussion

 

SystmOne and time out

Up to General discussion
September 11. 2017
Pete Scott

Has anyone come over an issue with SystmOne after it lockouts from not being used for more than half hour. It does not always come up with the error. But we have found this happened after we started rolling out the HSCIC IA V1 and then advised to uninstall the Oberthur Middleware by TPP as this was an issue they had come over, but this still does not work.

Attachments
September 12. 2017
Mamoona.Khalid

Hi,

We have the same issue as in the attachment. I wonder if its something to with the registry settings as below

Its set to 1800 seconds (30 mins) by default as below on Normal and Session Mode

The error could also be due to smartcard drivers however i am due to visit a site and investigate on Thursday.

 

IdleWaitPeriodInSeconds

(REG_DWORD)

1800

The time (in seconds) that the user session is allowed to be idle before it ‘Windows locks’ the screen (1800s = 30m).

IT Administrators might want to review this timing in relation to individual needs within the service.

 

This timer is active in ‘Session Lock’ and ‘Normal’ modes, and ‘Mobility mode’ whilst the Smartcard is present. In ‘Mobility mode’ whilst the Smartcard is removed, the IA v2 mobility idle timer takes over and ‘IdleWaitPeriodInSeconds’ is stopped.

September 12. 2017
Pete Scott

Thanks Khalid if you could let us know your outcome it maybe helpful

September 14. 2017
Mamoona.Khalid

Hi Pete, Do you have access to Slack or an email where i can invite you

It's where we have Identity Agent issues and discussions which may help also.

September 29. 2017
Pete Scott

Yes I do have log in to Slack

 

pete.scott@nhs.net

Powered by Ploneboard