Cockpit sso plugin - Authentication failed: Timeout

Hi Everyone,

These past few days, I have been trying to debug an issue that occurred several times.

The issue is that I am not able to connect with cockpit SSO plugin after reinstalling the server.
reinstallation is required occasionally for running tests.
Before reinstalling the server, I deleted the host from Foreman. (hammer host delete --id 79)
Please note that connecting directly with DNS/IP on 9090 port does work.

On the first installation of the server and connecting it to FOREMAN, I was able to log in with SSO plugin.
The cockpit package was also installed.

I have tried to zero in on the problem in different ways:

  1. Made sure that were not any duplicate DNS.
  2. Created a new network card.
  3. Didn’t see any login attempts on the designated server.
  4. Selinux disabled
  5. firewalld disabled

The versions I’m using:
FOREMAN - 3.3.0
Katello - 4.5.0

Copied logs from FOREMAN server:
Sep 05 00:51:55 sdl-foreman cockpit-ws[22093]: INFO: Running foreman-cockpit-session with settings from /etc/foreman/cockpit/foreman-cockpit-session.yml:
Sep 05 00:51:55 sdl-foreman cockpit-ws[22093]: {:foreman_url=>“https://sdl-foreman.ilntsur.loc”, :s sl_ca_file=>"/etc/pki/katello/certs/katello-server-ca.crt", :ssl_certificate=>"/etc/foreman/client_ cert.pem", :ssl_private_key=>"/etc/foreman/client_key.pem"}
Sep 05 00:51:55 sdl-foreman smart-proxy[1315]: 10.8.0.48 - - [05/Sep/2022:00:51:55 IDT] “GET /dynfl ow/tasks/count?state=running HTTP/1.1” 200 29
Sep 05 00:51:55 sdl-foreman smart-proxy[1315]: - → /dynflow/tasks/count?state=running
Sep 05 00:52:25 sdl-foreman cockpit-ws[1344]: foreman-cockpit-session: session timed out during authentication
Sep 05 00:52:25 sdl-foreman cockpit-ws[1344]: foreman-cockpit-session: authentication timed out

Any help will be much appreciated!

Thanks in advance,
Shay

What is this cockpit SSO plugin?

cockpit SSO integration is not a plugin?
when you click on web console at ths host details is suppose to connect you with SSO to cockpit.

Update but not yet the solution.
When I’m trying to schedule remote job.
The job stuck, I see a blank screen.

also adding more logs from the foreman server

ep 05 14:12:43 sdl-foreman smart-proxy[35051]: 10.8.0.48 - - [05/Sep/2022:14:12:43 IDT] “GET /dynflow/tasks/af9dfc9e-393b-42d8-8ebf-eceb2d63c622/status HTTP/1.1” 200 2771
Sep 05 14:12:43 sdl-foreman smart-proxy[35051]: - → /dynflow/tasks/af9dfc9e-393b-42d8-8ebf-eceb2d63c622/status
Sep 05 14:12:45 sdl-foreman smart-proxy[35051]: 10.8.0.48 - - [05/Sep/2022:14:12:45 IDT] “GET /dynflow/tasks/af9dfc9e-393b-42d8-8ebf-eceb2d63c622/status HTTP/1.1” 200 2771
Sep 05 14:12:45 sdl-foreman smart-proxy[35051]: - → /dynflow/tasks/af9dfc9e-393b-42d8-8ebf-eceb2d63c622/status
Sep 05 14:12:46 sdl-foreman smart-proxy[35051]: 10.8.0.48 - - [05/Sep/2022:14:12:46 IDT] “GET /dynflow/tasks/af9dfc9e-393b-42d8-8ebf-eceb2d63c622/status HTTP/1.1” 200 2771
Sep 05 14:12:46 sdl-foreman smart-proxy[35051]: - → /dynflow/tasks/af9dfc9e-393b-42d8-8ebf-eceb2d63c622/status
Sep 05 14:12:48 sdl-foreman smart-proxy[35051]: 10.8.0.48 - - [05/Sep/2022:14:12:48 IDT] “GET /dynflow/tasks/af9dfc9e-393b-42d8-8ebf-eceb2d63c622/status HTTP/1.1” 200 2771
Sep 05 14:12:48 sdl-foreman smart-proxy[35051]: - → /dynflow/tasks/af9dfc9e-393b-42d8-8ebf-eceb2d63c622/status

Hi all again,
Found the solution
clear the host from this file
/usr/share/foreman-proxy/.ssh/known_hosts