PWM Idle Time security violation

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open PWM login page.

What is the expected output? What do you see instead?
Expected: PWM Login Page
Seen: A security violation has occurred. Please try again later. { 5063 
ERROR_SECURITY_VIOLATION (session idle time (34m) is longer than maximum idle 
time age) }

What version of PWM are you using?
1.7.0

What ldap directory and version are you using?
openldap

Please paste any error log messages below:
A security violation has occurred. Please try again later. { 5063 
ERROR_SECURITY_VIOLATION (session idle time (34m) is longer than maximum idle 
time age) }

Original issue reported on code.google.com by g...@sandydproductions.com on 27 Nov 2013 at 7:11

[GoogleCodeExporter]

Please check your clock synchronization. If that doesn't help, provide a long 
enough log (from PWM start until the incident occurs) at TRACE level and steps 
to reproduce.

Original comment by menno.pi...@gmail.com on 27 Nov 2013 at 7:21

• Changed state: NeedInfo

[GoogleCodeExporter]

This is most likely working as designed.  If a session is used that is still a 
valid tomcat session, but hasn't served a page since the maximum idle time ago, 
then you'll see this error.  Most likely reasons for the tomcat session to 
still be valid is that a resource (perhaps under /public/resources/* has been 
retrieved (keeping the tomcat-level session active) but not a main pwm page.  
This is either due to customiation or a bug, and we would need a log trace to 
see this.  The other reason is a tomcat shutdown/restart which preserves old 
sessions until the server has been up and they idle out again.

Original comment by jrivard on 2 Dec 2013 at 7:16

[GoogleCodeExporter]

This happened for me during the configuration process.  Is there a way to get 
around this behavior?

Original comment by da...@optionmetrics.com on 3 Dec 2013 at 9:53

[GoogleCodeExporter]

This issue has been resolved in the current nightly builds.

Original comment by jrivard on 3 Apr 2014 at 7:32

• Changed state: Fixed

[GoogleCodeExporter]

I am seeing this error as well I have tried v1.7 and 1.7.1 and in both I see 
the issue
A security violation has occurred. Please try again later. { 5063 
ERROR_SECURITY_VIOLATION (current network address 'xxx.xxx.66.205' has changed 
from original network address 'xxx.xxx.15.134') }
This issue only occurs after idle session expires and redirected to anther page.
User is unabled to access pwm page until browser cache is cleared

Original comment by lilia...@gmail.com on 30 Sep 2014 at 3:10