Integration testing with cockpit, how to deal with authentication?
by Daniel Hilst Selli
Hi everybody.
I have been playing with cockpit for some time. Now I have a little library that
create processes in the backend, which keep running until I stop then, so I
start wondering about how to do integration testing with cockpit, ...
In cockpit I have these constraints:
- cockpit.js is served by cockpit-ws,
- A pam session is created when user login on web interface,
At the most what I have is some function calls that have side effects on
backend. My testing would be checking for these side effects on the backend,
like checking if some process started, or finished, or if some file was created,
or if a database table was populated.. Usually we would execute tests over
nodejs but I don't now how to deal with pam session ...
Cheers,
Daniel
5 years, 5 months
Menu index URL
by Edoardo Spadoni
Hi,
I would like to handle a menu item URL like this (in manifest.json), the
second one:
"menu": {
"index": {
"label": "System",
"order": 10
},
"../my-module#/path": {
"label": "Applications",
"order": 20
}
}
The URL is handled, but the # is escaped into %23 then the module is not
available. Is there a way to unescape that and keep the URL as in the
manifest?
Thanks,
Edoardo Spadoni
5 years, 5 months
new privacy policy for the Cockpit project
by Garrett LeSage
Hi everyone!
You've probably noticed how everyone else is updating their privacy
policy. The Cockpit Project is updating our own too.
There are manymore details in the privacy policy, but here's a quick
summary:
1. In most circumstances, the Cockpit Project does not actively collect
your information.
2. We do, however, use mailing lists, IRC, and GitHub — and all of these
third party services require at least a little bit of your personal
informationto function.
3. The website is static, doesn't track, and does not set cookies.
4. The website makes use of embedded videos, especially in blog posts.
These videos are hosted by YouTube, a Google company, which would see
your IP address when the videos are loaded. We have turned off cookies
for these videos.
5. We may collect some small amounts of personal information from people
at conferences, during usability tests, or to respond back to someone
over email. This information usually consists of names, email addresses,
and sometimes a fewother personal details.
We have a new page that outlines the above and goes into more detail
(including a large helping of legalese) on our website at:
https://cockpit-project.org/privacy.html
On the privacy page, there are links to contact third parties (and to
read their own privacy policies too), as well as a lot of details that
could cover all sorts of situations.
Thanks for reading!
Garrett
5 years, 6 months
Call for feedback: Seamless Single Sign On with Cockpit
by Marius Vollmer
Hi,
I have been learning about how to intergrate Cockpit with management
systems like ManageIQ, oVirt, and Foreman.
Such integration already exists for ManageIQ and oVirt, but the one for
Foreman isn't as seamless as the rest. So I have been digging through
the code and asked around, and produced this:
https://github.com/mvollmer/seamless-cockpit/
This should be the starting point for improving the seamlessness of
Cockpit in Foreman, and maybe for other such integrations.
If you are interested, it would be great if you could have a look and
try to run the code. There are likely a lot of details that work for me
but not for everyone. Any feedback is welcome!
Thanks!
5 years, 6 months
Cockpit 169 released
by Martin Pitt
http://cockpit-project.org/blog/cockpit-169.html
Cockpit is the modern Linux admin interface. We release regularly. Here
are the release notes from version 169.
Storage: Offer installation of NFS client support
-------------------------------------------------
The "NFS Mounts" pane on the Storage page now shows an "Install NFS Support"
button if the necessary packages are not already available.
See it in action: https://youtu.be/Gaioqm7sLEo
System: Request FreeIPA SSL certificate for Cockpit's web server
----------------------------------------------------------------
When enrolling into a FreeIPA domain, an SSL certificate is requested from the
IPA server and stored in /etc/cockpit/ws-certs.d/10-ipa.cert. Cockpit's web
server will then use that certificate instead of the default self-signed one.
The IPA server's certificate authority is trusted by default and accepted by
web browsers, OpenSSL, curl, and other network clients.
Services: Show unit relationships
---------------------------------
The details of a systemd service now shows dependency, ordering, and other
relationships to units:
Screenshot: https://cockpit-project.org/images/services-relationships.png
Provide motd help about how to access cockpit
---------------------------------------------
Cockpit now provides an `/etc/motd.d/cockpit` motd message that explains how to
enable and start Cockpit if it's not running, or how to access it if it is
running.
This requires PAM 1.3.1 and enabling the `pam_motd` module:
session optional pam_motd.so
Get it
------
You can get Cockpit here:
http://cockpit-project.org/running.html
Cockpit 169 is available in Fedora 28:
https://bodhi.fedoraproject.org/updates/cockpit-169-1.fc28
Or download the tarball here:
https://github.com/cockpit-project/cockpit/releases/tag/169
Take care,
Martin Pitt
5 years, 6 months
React
by Marek Libra
Hi,
bringing old question up again: Can Cockpit move to React from the
react-lite?
I hit an issue with reusing the patternfly-react library - some used
features are of latest React versions, not available in react-lite. And
there are no known plans to adopt them to the react-lite [1] [2].
React is recently 16.3.2, latest react-lite implements scope of 15.x.
I believe Cockpit can still live with that. But from longer perspective it
might be annoying to deal with compatibility.
Marek
[1] https://github.com/Lucifier129/react-lite/issues/126
[2] see latest commit dates:
https://github.com/Lucifier129/react-lite/commits/master
5 years, 6 months
Cockpit 168 released
by Martin Pitt
http://cockpit-project.org/blog/cockpit-168.html
Cockpit is the modern Linux admin interface. We release regularly. Here
are the release notes from version 168.
Improve checks for root privilege availability
----------------------------------------------
Many actions, like joining an IPA domain or rebooting, can only be performed by
an administrator (root user).
Cockpit previously checked if the user was a member of the wheel (used in Red
Hat Enterprise Linux, CentOS, and Fedora) or sudo (used in Debian and Ubuntu)
groups to enable these actions. Simple group checking was insufficient, as
different group names are used by other operating systems and configurations,
or a system might be set up to rely on custom user-based sudo rules.
Cockpit no longer makes assumptions about special groups. Now, Cockpit simply
checks if the user is capable of running commands as root.
As a result of this fix, privileged operations now work by default with
FreeIPA, which uses the admins(a)domain.name group.
Get it
------
You can get Cockpit here:
http://cockpit-project.org/running.html
Cockpit 168 is available in Fedora 28:
https://bodhi.fedoraproject.org/updates/cockpit-168-1.fc28
Or download the tarball here:
https://github.com/cockpit-project/cockpit/releases/tag/168
Take care,
Martin Pitt
5 years, 6 months