Description of problem:
ERF42-4995 [Foreman::Exception]: Invalid authenticity token message displayed with traceback, If I re-login the machine after the session out.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install the satellite with 6.8
2. wait for session timed out.
3. After session timed out, re-login the machine again, then we get ERF42-4995 [Foreman::Exception]:.
Some exceptions observed, If we re-login the machine after the session out.
No exception should come if we re-login the machine after the session timed out.
What authentication source is the user which is timing out using? Is any external authentication enabled?
Does this occur for all users or only a specific one?
How long passed between the timeout and the re-login attempt?
Additionally, are you certain this isn't also the case in 6.7 and older? https://projects.theforeman.org/issues/10577 seems like a similar issue and is 5 years old.
(In reply to Tomer Brisker from comment #10)
> Additionally, are you certain this isn't also the case in 6.7 and older?
> https://projects.theforeman.org/issues/10577 seems like a similar issue and
> is 5 years old.
I am not sure about other versions but I didn't face this issue on 6.7.
Please reply to the questions in comment #9 as well. Also, did you have multiple tabs open by any chance when the session timed out?
Connecting redmine issue https://projects.theforeman.org/issues/10577 from this bug
Upstream bug assigned to firstname.lastname@example.org
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/10577 has been resolved.
Verified on 6.8 Snap14.
1: Didn't see the foreman-exception after re-login the ipv6 machine after autologous.
2: # rpm -qa|grep foreman-2.1.2.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.