[Nagiosplug-help] check-http with client certificate authoriz ation
Fabian.Pehla at Dregis.com
Thu Apr 17 06:51:11 CEST 2003
I've implemented a check_http Plugin which is - besides some other new
features - able to use client certifictes for authentication.
This plugin implements nearly all options which are supported by the
original plugin from 1.3.0 release, but the implementation is quite
different. It is based on OpenSSL functionality, so other SSL
implementations won't work
The "Error in recv()" you mentioned below just means that the server's
request for a client certificate is not handled by the plugin from release
1.3.0. I assume your server requests a client certificate prior to asking
for basic authentication, am I right?
If you're interested I may make my Version of check_http available on
From: Heckert, Torsten [mailto:torsten.heckert at sap.com]
Sent: Thursday, April 17, 2003 3:30 PM
To: 'nagiosplug-help at lists.sourceforge.net'
Subject: [Nagiosplug-help] check-http with client certificate
I am currently evaluating to monitor some of our webservers using nagios.
Some of them offer SingleSignOn by accepting clientside certificates. It is
also possible to log on using basic authentication.
When I access these servers check_http seems to crash:
[server accepting SSO]
> ./check_http -H sapneth1.wdf.sap.corp -S -v -a xxxxx:yyyyy
SSL seeding: OK
Error in recv()
[same server using http]
> ./check_http -H sapneth1.wdf.sap.corp -p 1080 -a xxxxx:yyyyy
HTTP ok: HTTP/1.1 200 OK - 7.382 second response time |time= 7.382
[server without SSO using https]
> ./check_http -H www001.sap-ag.de -S
HTTP ok: HTTP/1.1 200 OK - 0.727 second response time |time= 0.727
Version: check_http (nagios-plugins 1.3.0) 1.24
Is there a possibibilty for a workaround or a different plugin that may
solve this issue?
Thanks in advance,
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
Nagiosplug-help mailing list
Nagiosplug-help at lists.sourceforge.net
::: Please include plugins version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Help