Cacti - TACACS+ Authentication

Anything that you think should be in Cacti.

Moderators: Moderators, Developers

Author
Message
Palermo
Cacti User
Posts: 87
Joined: Thu Sep 11, 2008 11:48 pm

#16 Post by Palermo » Fri Feb 12, 2010 7:24 am

Hi can you make a sort of manual to how to link cacti to tacacs+?

Thx in advanced

User avatar
_raindrop18
Cacti User
Posts: 194
Joined: Thu Jan 29, 2009 5:52 pm
Location: US

#17 Post by _raindrop18 » Thu Aug 12, 2010 12:59 pm

any one has simple instruction how to integrate Cacti login with Cisco ACS.
thanks!!!

malgoe
Posts: 49
Joined: Tue Nov 08, 2011 11:35 am

Re: Cacti - TACACS+ Authentication

#18 Post by malgoe » Tue Mar 20, 2012 5:46 am

I know the thread is somewhat old, but I was searching for a solution to this and stumbled upon this guide: http://www.m00nie.com/2011/01/cacti-aut ... cisco-acs/

I have not had a chance to try it out yet. One thing I am wondering is how to map users to permissions in Cacti? Do I need to add a user with the same username in both Cacti and ACS for things to work?

havok1977
Posts: 49
Joined: Fri Apr 08, 2005 1:41 pm

Re: Cacti - TACACS+ Authentication

#19 Post by havok1977 » Thu Jul 04, 2013 12:30 pm

malgoe wrote:I know the thread is somewhat old, but I was searching for a solution to this and stumbled upon this guide: http://www.m00nie.com/2011/01/cacti-aut ... cisco-acs/

I have not had a chance to try it out yet. One thing I am wondering is how to map users to permissions in Cacti? Do I need to add a user with the same username in both Cacti and ACS for things to work?
I'm looking into the same thing, at my company we already have a Cacti server meant for internal usage authenticating via TACACS+ using Apache + mod_xradius, and we have been forced to maintain the two user databases to get user permissions to work properly.

This is not too bad for internal use, where there are under 30/40 users that need access; yet on our customer facing Cacti server there are hundreds of users to keep track of and the administrative overhead becomes unmanageable. And at this point we would prefer to keep authentication and permissions in a single repository to avoid duplication of effort.

Anyone knows if there is a way of achieving this?

Post Reply