Excellent.
Will this also work with self-signed, or would you simply specify
validate false?
Cheers,
PC
On Tue, Oct 9, 2018 at 7:38 PM Stef Walter <swalter(a)redhat.com> wrote:
>
> On 08/10/2018 22:24, Paul Cuzner wrote:> Hi,
> >
> > I can see in the docs that there is http based support for cockpit to
> > interact with HTTP endpoint, which works fine.
> >
> > Could anyone clarify the approach when the endpoint that the plugin
> > needs to interact with is https instead of http (I'm assuming most
> > REST interfaces will be secure at least over the wire!)?
>
> Whoops, looks like documentation for the HTTPS part of cockpit.http() is
> missing. I've opened a pull request to document each option:
>
>
https://github.com/cockpit-project/cockpit/pull/10249
>
> The pull request includes an example that looks something like this:
>
> http = cockpit.http({
> "address": "localhost",
> "headers": {
> "Authorization": "Basic dXNlcjpwYXNzd29yZA=="
> },
> "port": 443,
> "tls": {
> "validate": true,
> "authority": {
> "file": "/etc/pki/tls/certs/ca-bundle.crt",
> },
> "certificate": {
> "data": "-----BEGIN CERTIFICATE-----\nMIIDsDCCA..."
> },
> "key": {
> "data": "-----BEGIN RSA PRIVATE
KEY-----\nMIIEogIBA..."
> }
> }
> });
>
> Hope that helps,
>
> Stef