Re: [Nagios-users] Nagios 3 ACK author

2009-05-08 Thread Max
If your accounts are in LDAP you can do some scripting to sync between
LDAP and Nagios.  Since it seems you more care about individual
usernames but not strong security, you can just make the password the
same for each account when you create the HTTP AUTh account on the
Nagios poller.

Either that or you can use the same philosophy, script to sync Nagios
user accounts from LDAP queries, and then use one of the Apache LDAP
authentication modules to authenticate the user so they use their real
password to authenticate.

- Max

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] Nagios 3 ACK author

2009-05-08 Thread Andreas Ericsson
Sven Wiedeck wrote:
> Hi,
> 
> thanks for the replies but we don't want to create user accounts for > 
> 30 people if it's not absolutely neccesary.
> 
> So the auto-login is the only way so far...
>

No can do then. You can lock the author-field, but if everyone are
authenticated as the same person, using the exact same credentials,
there's no way of telling them apart automatically. You *could* add
a check to see if the field isn't changed. That requires basic C
programming skills and a rudimentary grasp of how HTML works when
posting form data. If you still want help with that, you can probably
contact op5 and get a consultancy price. I doubt it'll be of much use
to the community, so it *will* come with a price-tag.

/Andreas

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] Nagios 3 ACK author

2009-05-08 Thread Sven Wiedeck

Hi,

thanks for the replies but we don't want to create user accounts for >  
30 people if it's not absolutely neccesary.


So the auto-login is the only way so far...

Sven


Am 08.05.2009 um 13:11 schrieb Jim Avery:


2009/5/8 Sven Wiedeck :

Hi everybody,
a few words before:
-> we're running a Nagios 3 installation
-> logins are disabled - everybody is nagiosadmin per default (only
internally reachable)
Now I'm searching for a possibility to force the users to enter  
their name

when they acknowledge a problem.
Currenty the author name is set to the default login per default
(nagiosadmin).
Some people leave this name in there and we can't see who has ack'ed.
Is there any way to leave the author name empty that Nagios rejects  
the ack

without entering a name?
Thanks a lot,
Sven



I guess you need to look in /usr/local/nagios/etc/cgi.cfg:

 # LOCK AUTHOR NAMES OPTION
 # This option determines whether users can change the author name
 # when submitting comments, scheduling downtime.  If disabled, the
 # author names will be locked into their contact name, as defined  
in Nagios.

 # Values: 0 = allow editing author names
 # 1 = lock author names (disallow editing)

 lock_author_names=1

And configure Nagios so that people will login using their own  
username.


hth,

Jim


Sven
IT/Administrator

wunderloop media services GmbH
Holzdamm 18
20099 Hamburg

T +49 (0)40 - 432 07 826
F +49 (0)40 - 432 07 799
E sven.wied...@wunderloop.com

www.wunderloop.de

Sitz und Handelsregister: AG Hamburg, HRB 80 530
Geschäftsführung: Torsten Ahlers, Sven Bagemihl, Frank Conrad, Dr.  
Christoph Bauer


This e-mail is confidential and is intended for the addressee(s) only.  
If you are not the named addressee you may not use it, copy it or  
disclose it
to any other person. If you received this message in error please  
notify the

sender immediately.

P please consider the environment - do you really need to print this  
email?


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] Nagios 3 ACK author

2009-05-08 Thread Jim Avery
2009/5/8 Sven Wiedeck :
> Hi everybody,
> a few words before:
> -> we're running a Nagios 3 installation
> -> logins are disabled - everybody is nagiosadmin per default (only
> internally reachable)
> Now I'm searching for a possibility to force the users to enter their name
> when they acknowledge a problem.
> Currenty the author name is set to the default login per default
> (nagiosadmin).
> Some people leave this name in there and we can't see who has ack'ed.
> Is there any way to leave the author name empty that Nagios rejects the ack
> without entering a name?
> Thanks a lot,
> Sven


I guess you need to look in /usr/local/nagios/etc/cgi.cfg:

  # LOCK AUTHOR NAMES OPTION
  # This option determines whether users can change the author name
  # when submitting comments, scheduling downtime.  If disabled, the
  # author names will be locked into their contact name, as defined in Nagios.
  # Values: 0 = allow editing author names
  # 1 = lock author names (disallow editing)

  lock_author_names=1

And configure Nagios so that people will login using their own username.

hth,

Jim

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] Nagios 3 ACK author

2009-05-08 Thread Andreas Ericsson
Sven Wiedeck wrote:
> Hi everybody,
> 
> a few words before:
> -> we're running a Nagios 3 installation
> -> logins are disabled - everybody is nagiosadmin per default (only 
> internally reachable)
> 
> Now I'm searching for a possibility to force the users to enter their 
> name when they acknowledge a problem.
> 
> Currenty the author name is set to the default login per default 
> (nagiosadmin).
> Some people leave this name in there and we can't see who has ack'ed.
> 
> Is there any way to leave the author name empty that Nagios rejects the 
> ack without entering a name?
> 

The simple way is to create per-user accounts with admin rights and
then create contacts with the same names as the usernames you set.
The difficult way is to hack the CGI's and recompile.

-- 
Andreas Ericsson   andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225  Fax: +46 8-230231

Register now for Nordic Meet on Nagios, June 3-4 in Stockholm
 http://nordicmeetonnagios.op5.org/

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


[Nagios-users] Nagios 3 ACK author

2009-05-08 Thread Sven Wiedeck

Hi everybody,

a few words before:
-> we're running a Nagios 3 installation
-> logins are disabled - everybody is nagiosadmin per default (only  
internally reachable)


Now I'm searching for a possibility to force the users to enter their  
name when they acknowledge a problem.


Currenty the author name is set to the default login per default  
(nagiosadmin).

Some people leave this name in there and we can't see who has ack'ed.

Is there any way to leave the author name empty that Nagios rejects  
the ack without entering a name?


Thanks a lot,

Sven--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null