While polling for authn/registration state changes. The globally defined timeout periods for these actions where not tested explicitly. This PR ensures we start testing if the timeout period is expired.
For registration, I added a new timeout error page. For this a new translation was added @pmeulen do you agree with my proposed translations? If not feel free to suggest better ones. I based these off the authn ones.
An offset time is substracted from the hard timeout time. This makes the timeout occur a couple of seconds before the actual timeout would take place. This prevents user actions taking place right before expiration time from erroring.
See: https://www.pivotaltracker.com/story/show/188205272 (note that the story mentions registration/authentication sessions. These are not to be confused with state/php sessions. But they are the 'session' in which an authentication or a registration takes place.)
While polling for authn/registration state changes. The globally defined timeout periods for these actions where not tested explicitly. This PR ensures we start testing if the timeout period is expired.
For registration, I added a new timeout error page. For this a new translation was added @pmeulen do you agree with my proposed translations? If not feel free to suggest better ones. I based these off the authn ones.
An offset time is substracted from the hard timeout time. This makes the timeout occur a couple of seconds before the actual timeout would take place. This prevents user actions taking place right before expiration time from erroring.
See: https://www.pivotaltracker.com/story/show/188205272 (note that the story mentions registration/authentication sessions. These are not to be confused with state/php sessions. But they are the 'session' in which an authentication or a registration takes place.)