If you're using Foreman Cockpit and your hosts use Cockpit newer than
0.78, you probably have noticed the plugin does not work. That's because
of a change of the URL endpoints the plugin uses to connect to Cockpit.
I got in touch with the Cockpit team, and tried to find a way to support
both in foreman_cockpit, but there are a number of limitations that make
this very hard to do*, especially since we don't store Cockpit
credentials in Foreman.
As far as I understood, some of the current Cockpit URLs are going to be
stable endpoints, and they've taken our use case to improve their
product and either redirect old URLs, offer a 'version' header… in
future versions.
The newest version of Foreman Cockpit that supports the new set of URLs
will be published shortly after these two pull requests are merged:
Thanks for reading, let me know if you have any questions, want to help,
etc…
Non-existing URLs point to Cockpit login, and only after the login
you'd get a 404, or a redirect to a working page that may not have to
do with the original URL.
This update is very much appreciated. I had been trying to get this working
last week in my Foreman project and thought I may have been missing
something in the configuration steps.
I have yet to get it working but I will be following updates that follow in
regards to Cockpit + Foreman.
Related to this… is there any work around being able to use the smart
proxy as a bridge? So, foreman is in one network segment and the host
with cockpit in a different network segment?
> This update is very much appreciated. I had been trying to get this working
> last week in my Foreman project and thought I may have been missing
> something in the configuration steps.
>
> I have yet to get it working but I will be following updates that follow in
> regards to Cockpit + Foreman.
Tatenda, foreman-cockpit 2.0.1 deb and rpm packages are out. It's on
1.9, 1.10, 1.11 and nightly repositories.
> Related to this… is there any work around being able to use the smart proxy
> as a bridge? So, foreman is in one network segment and the host with cockpit
> in a different network segment?
I chatted with some people on the #cockpit IRC but this doesn't seem to
be an option yet. They're exploring how to do it, so I gave them my use
case, which I hope they'll take into account when designing remote
authentication in Cockpit.
