Page 1 of 1

Feature Request: TACACS/TACACS+

Posted: Tue Dec 20, 2016 9:05 am
by grigoryx
I would be cool if TACACS/TACACS+ would be supported in next ROS version. Is it planned in ROSv6/ROSv7 or not?

Re: Feature Request: TACACS/TACACS+

Posted: Tue Dec 20, 2016 11:15 am
by janisk
Isn't that a protocol that RADIUS was/is based on?

Re: Feature Request: TACACS/TACACS+

Posted: Tue Dec 20, 2016 12:46 pm
by paoloaga
I would be cool if TACACS/TACACS+ would be supported in next ROS version. Is it planned in ROSv6/ROSv7 or not?
Why don't you just use RADIUS? I wrote a TACACS server for dial-up connections early in 1996 ... switched to RADIUS around year 2000.

Re: Feature Request: TACACS/TACACS+

Posted: Fri Dec 23, 2016 7:25 am
by agfjpcs
Isn't that a protocol that RADIUS was/is based on?

Wow.... Bit surprised to see a MikroTik employee asking this sort of question

Snip from http://www.tacacs.net/docs/TACACS_Advantages.pdf


The primary functional difference between RADIUS and
TACACS+ is that TACACS+ separates out the Authorization
functionality, where RADIUS combines both Authentication and
Authorization. Though this may seem like a small detail, it makes
a world of difference when implementing administrator AAA in a
network environment.

RADIUS doesn’t log the
commands used by the
administrator. It will only log
the start, stop, and interim
records of that session. This
means that if there are two or
more administrators logged at
any one time, there is no way
of telling which administrator
entered which commands.
RADIUS can include privilege information in the authentication reply; however, it can only provide the
privilege level, which means different things to different vendors. Because there is no standard between
vendor implementations of RADIUS authorization, each vendor’s attributes often conflict, resulting in
inconsistent results. Even if this information were consistent, the administrator would still need to manage the
privilege level for commands on each device. This will quickly become unmanageable.
RADIUS doesn’t log the commands used by the administrator. It will only log the start, stop, and interim
records of that session. This means that if there are two or more administrators logged at any one time, there
is no way to tell from the RADIUS logs which administrator entered which commands.



TACACS+ is far better than RADIUS if you need more than a simple 'Oh yep, that user account is allowed'

Re: Feature Request: TACACS/TACACS+

Posted: Fri Dec 23, 2016 10:51 am
by barkas
Tacacs is the proper solution for network device user management.

I would very much like to have that, too.

Re: Feature Request: TACACS/TACACS+

Posted: Wed Dec 28, 2016 10:01 am
by janisk
Isn't that a protocol that RADIUS was/is based on?

Wow.... Bit surprised to see a MikroTik employee asking this sort of question

Snip from http://www.tacacs.net/docs/TACACS_Advantages.pdf


The primary functional difference between RADIUS and
TACACS+ is that TACACS+ separates out the Authorization
functionality, where RADIUS combines both Authentication and
Authorization. Though this may seem like a small detail, it makes
a world of difference when implementing administrator AAA in a
network environment.

RADIUS doesn’t log the
commands used by the
administrator. It will only log
the start, stop, and interim
records of that session. This
means that if there are two or
more administrators logged at
any one time, there is no way
of telling which administrator
entered which commands.
RADIUS can include privilege information in the authentication reply; however, it can only provide the
privilege level, which means different things to different vendors. Because there is no standard between
vendor implementations of RADIUS authorization, each vendor’s attributes often conflict, resulting in
inconsistent results. Even if this information were consistent, the administrator would still need to manage the
privilege level for commands on each device. This will quickly become unmanageable.
RADIUS doesn’t log the commands used by the administrator. It will only log the start, stop, and interim
records of that session. This means that if there are two or more administrators logged at any one time, there
is no way to tell from the RADIUS logs which administrator entered which commands.



TACACS+ is far better than RADIUS if you need more than a simple 'Oh yep, that user account is allowed'
while your whole answer is based on TACACS+ that is later creation than RADIUS. However, DIAMETER is even newer and addresses many drawbacks of RADIUS and is compatible with the RADIUS.

and on the off-note, I am sure you know what sarcasm is.

Re: Feature Request: TACACS/TACACS+

Posted: Mon Apr 24, 2017 11:53 pm
by TheIPGuy
RADIUS has it's place, however, I think we can agree from a network administration perspective TACACS+ does have some nice features. One such feature is extremely granular centralized command authorization based on user permissions assigned by the server. Also, Tacacs was ported to linux, all though a bit roughly, via tac_plus. RADIUS user authentication for management purposes is nice if you want a read only or read/write access only, but is lacking when more granular control is required. Let's please keep a constructive dialog going on this issue as RADIUS and TACACS were intended for different purposes fundamentally. Sarcasm from a Mikrotik employee to mock a contributor on a valid point is childish.


+1 for TACACS support

Re: Feature Request: TACACS/TACACS+

Posted: Thu Jul 20, 2017 3:05 pm
by bruins0437
+1 for TACACS/TACACS+ support

Re: Feature Request: TACACS/TACACS+

Posted: Mon Jul 31, 2017 3:11 am
by tricksol
+1 for TACACS/TACACS+ support

Re: Feature Request: TACACS/TACACS+

Posted: Mon Aug 07, 2017 3:54 pm
by eric101
+1 for tacacs+ support, I think this would make a lot of people happy.

Re: Feature Request: TACACS/TACACS+

Posted: Wed Aug 23, 2017 10:57 am
by gidoos
+1 for this. Will defnitely be a big plus point for big networks.

Re: Feature Request: TACACS/TACACS+

Posted: Mon Sep 18, 2017 5:48 pm
by YourWordIsTruth
+1 for TACACS+ support, many companies don't consider your product, if you will, "Enterprise Grade", without TACACS+ support and frankly with security being the #1 issue in the enterprise TACACS+ is needed to not only secure a multitude of devices in complex networks, but also to provide auditing trails of admin usage when those pesky auditors come around yearly/quarterly :-)

Re: Feature Request: TACACS/TACACS+

Posted: Sun Oct 22, 2017 1:06 am
by branto
+1 for this this request. TACACS+ also encrypts the communications channel between client and server; RADIUS does not.

Re: Feature Request: TACACS/TACACS+

Posted: Mon Oct 23, 2017 1:38 am
by idlemind
I wonder if IPSec could be used to secure the RADIUS traffic between endpoints and an auth server. This would only cover the encryption side of the discussion not the feature differences.

Re: Feature Request: TACACS/TACACS+

Posted: Fri May 25, 2018 12:43 pm
by tonny
+1 for TACACS/TACACS+ support

Re: Feature Request: TACACS/TACACS+

Posted: Fri May 25, 2018 1:26 pm
by mlenhart
+1 for TACACS+ support

Re: Feature Request: TACACS/TACACS+

Posted: Fri May 25, 2018 11:50 pm
by networkfudge
+ 1

Re: Feature Request: TACACS/TACACS+

Posted: Fri Aug 31, 2018 3:25 pm
by sep
+1 for TACACS+ support

Re: Feature Request: TACACS/TACACS+

Posted: Fri Aug 31, 2018 3:30 pm
by StubArea51
I would like to see TACACS+ support as well. Being able to restrict the commands that a user can execute is incredibly important.

Especially with all of the attacks against MikroTik devices - it provides another layer of protection in addition to the firewall if a lower level user account is compromised.

Re: Feature Request: TACACS/TACACS+

Posted: Fri Aug 31, 2018 3:56 pm
by Dude2048
+1 Tacacs

Re: Feature Request: TACACS/TACACS+

Posted: Mon Sep 03, 2018 7:42 pm
by TheCiscoGuy
At least disable the local users if AAA is configured and reachable. TACACS would be nice, but the current radius is functional, just doesnt disable local accounts.

Re: Feature Request: TACACS/TACACS+

Posted: Mon Sep 03, 2018 8:31 pm
by maznu
At least disable the local users if AAA is configured and reachable. TACACS would be nice, but the current radius is functional, just doesnt disable local accounts.
Why not just set your one local admin account to have an impossible IP address restriction, and then you've still got console-level access should your connectivity to TACACS go fubar...?

Re: Feature Request: TACACS/TACACS+

Posted: Tue Sep 18, 2018 4:51 pm
by caiot5
+1 for TACACS+ support.

Re: Feature Request: TACACS/TACACS+

Posted: Tue Sep 18, 2018 6:06 pm
by alessio79
+1 for TACACS+

Re: Feature Request: TACACS/TACACS+

Posted: Mon Oct 08, 2018 9:32 pm
by mAineAc
+1 on tacacs+ support.

Re: Feature Request: TACACS/TACACS+

Posted: Fri Nov 02, 2018 1:27 pm
by Faceless
+1 for TACACS+

Re: Feature Request: TACACS/TACACS+

Posted: Mon Nov 05, 2018 12:59 pm
by nz_monkey
+1 for TACACS+ support

Re: Feature Request: TACACS/TACACS+

Posted: Fri Jan 11, 2019 7:54 pm
by around
+1 for TACACS+ support

Re: Feature Request: TACACS/TACACS+

Posted: Fri Jan 11, 2019 7:59 pm
by around
+1 for TACACS+ support

Re: Feature Request: TACACS/TACACS+

Posted: Mon Jan 14, 2019 5:00 pm
by leoeletronics
+1 TACACS

Re: Feature Request: TACACS/TACACS+

Posted: Thu Jan 17, 2019 12:54 pm
by Kampfwurst
+1 TACACS

Re: Feature Request: TACACS/TACACS+

Posted: Sat Mar 02, 2019 8:49 pm
by Cha0s
+1 for TACACS+ support

Re: Feature Request: TACACS/TACACS+

Posted: Sun Mar 03, 2019 10:44 am
by Jotne
As long as Router OS does not log all commands run by who, I would also ask for TACACS support.

Re: Feature Request: TACACS/TACACS+

Posted: Sat Mar 09, 2019 3:50 pm
by nimbo78
As long as Router OS does not log all commands run by who I would also ask for TACACS support.
that's why +1 for TACACS+

Re: Feature Request: TACACS/TACACS+

Posted: Tue Apr 02, 2019 8:11 am
by TaBo
+1 for TACACS+

Re: Feature Request: TACACS/TACACS+

Posted: Sun Apr 07, 2019 10:32 pm
by mutinsa
+1.

Re: Feature Request: TACACS/TACACS+

Posted: Fri Dec 27, 2019 12:17 pm
by nimbo78
@normis
how about to add this feature?

Re: Feature Request: TACACS/TACACS+

Posted: Tue Jan 07, 2020 4:44 am
by SumNathan
+1 for TACACS+ support!
Really like being able to limit what commands a user can run (great for creating a backup user that can only run a backup command).

Re: Feature Request: TACACS/TACACS+

Posted: Tue Jan 07, 2020 1:07 pm
by aacable
+1 for TACACS+ support

I have TACASCS+ configured on Linux to authenticate / restrict sessions/cmd's on various switches. It really helps the admin when managing large enterprise. Plus we are now able to satisfy the external Audit team. Would love if its support adds in the TIK

Re: Feature Request: TACACS/TACACS+

Posted: Fri Mar 27, 2020 9:01 pm
by smirre
+1 for tacacs+ auth

Re: Feature Request: TACACS/TACACS+

Posted: Tue Jun 02, 2020 7:32 am
by jimmer
+1 for TACACS+ on RouterOS

Re: Feature Request: TACACS/TACACS+

Posted: Fri Dec 25, 2020 5:46 am
by daemontux
+1 for TACACS+ support

Re: Feature Request: TACACS/TACACS+

Posted: Wed Jan 06, 2021 1:35 pm
by antmix
+1 for TACACS+ support

Re: Feature Request: TACACS/TACACS+

Posted: Thu Jan 07, 2021 8:32 am
by zanswer
+1 for TACACS+ support!

Re: Feature Request: TACACS/TACACS+

Posted: Sun May 23, 2021 1:10 pm
by paulpaulpaul
+1 for TACACS

Any feedback about the plans of microtik would be highly desirable

Re: Feature Request: TACACS/TACACS+

Posted: Fri Jun 04, 2021 5:59 am
by babukvb
+1 for TACACS
Only this feature can help mikrotik continue in enterprise/telecom/ISP networks in India.

Re: Feature Request: TACACS/TACACS+

Posted: Thu Dec 16, 2021 12:29 pm
by grims
+1 for TACACS

Re: Feature Request: TACACS/TACACS+

Posted: Thu Dec 16, 2021 1:48 pm
by clambert
+1 for TACACS

Re: Feature Request: TACACS/TACACS+

Posted: Tue Apr 19, 2022 9:18 pm
by akschu
+1 for TACACS, I don't want to install radius just for Mikrotik and to have less functionality.

Re: Feature Request: TACACS/TACACS+

Posted: Tue Apr 19, 2022 9:28 pm
by rextended
-1 for TACACS
+1 for TACOS

How many just registered users just to put a +1, is all useless, you have only one device and don't count for anything.
Oh, am I wrong and have thousands of devices? Then you haven't figured out how it works!
Contact sales@mikrotik.com to request a quote on the desired feature, if feasible.

Re: Feature Request: TACACS/TACACS+

Posted: Wed Nov 02, 2022 10:06 am
by Pun1sh3r
+1 for TACACS+ in ROS6

Re: Feature Request: TACACS/TACACS+

Posted: Wed Nov 02, 2022 11:30 am
by rextended
Look, they were thinking about adding something to v6 right now...

Re: Feature Request: TACACS/TACACS+

Posted: Wed Nov 30, 2022 11:16 am
by amix
+1 for Tacacs support

Re: Feature Request: TACACS/TACACS+

Posted: Wed Feb 22, 2023 10:18 am
by kashifmax
1+ for tacacs

Re: Feature Request: TACACS/TACACS+

Posted: Thu Jul 27, 2023 6:42 pm
by enderst
+1 for Tacacs support

Re: Feature Request: TACACS/TACACS+

Posted: Thu Jul 27, 2023 7:16 pm
by Amm0
FWIW, I think folks should be clear as to what they are looking for here than just "+1"... I'm just not sure of the use-cases for "TACACS support" in 2023. Diameter was already a thing when this thread started and more modern than a 30 year old somewhat-Cisco specific protocol...

And support for any AAA protocol may not help that much since available RouterOS policy options are rather limited/course. e.g. command-level access control isn't something RouterOS supports today in the underlying policies, so is TACACS useful without that?

Re: Feature Request: TACACS/TACACS+

Posted: Sun Jul 30, 2023 10:49 pm
by dooh
Hi,

TAC/TAC+ should be added to Mikrotik devices as all (I really do not have any other equipment that does not know about AAA with tacacs) know how to use tacacs for remote AAA.

We use TACACS for all of our network equipment and just saw that Mikrotik does not use that. TACACS is the way to go for logging remote commands and restrict users.

Here is just a quick diff between TACACS+ and RADIUS from GPT:
The choice between TACACS+ (Terminal Access Controller Access Control System Plus) and RADIUS (Remote Authentication Dial-In User Service) for network equipment login depends on the specific requirements and priorities of the organization. Both protocols have their strengths, but TACACS+ is generally preferred over RADIUS for network equipment login in certain scenarios due to the following reasons:

1. Granular Access Control: TACACS+ offers more granular access control capabilities compared to RADIUS. It allows administrators to define detailed authorization policies on a per-user or per-group basis, specifying exactly what commands and network resources each user can access. This level of granularity is especially important in large enterprise networks with complex security requirements.

2. Separation of Authentication and Authorization: TACACS+ separates authentication and authorization functions, whereas RADIUS often combines them. This separation allows for a more secure implementation, as authentication can be handled centrally while authorization decisions are made locally on the network device. In contrast, RADIUS usually performs both authentication and authorization on the RADIUS server, potentially exposing the server to greater risks.

3. Enhanced Security: TACACS+ provides stronger security mechanisms, including end-to-end encryption of communication between the client and the TACACS+ server. This encryption ensures that sensitive data, such as user credentials, is protected from potential eavesdropping and tampering. While RADIUS can also support encryption, it is not a mandatory requirement, and some RADIUS implementations might not use it by default.

4. Accounting Flexibility: TACACS+ offers more comprehensive accounting features compared to RADIUS. It provides detailed logging of all user activities on the network device, offering valuable data for auditing and compliance purposes. While RADIUS can handle accounting as well, TACACS+ is known for its more robust accounting capabilities.

5. Vendor Support: While both TACACS+ and RADIUS are widely supported by networking vendors, TACACS+ is favored in environments with Cisco network equipment. Cisco devices, in particular, have native support for TACACS+ and offer more features and integration options when using TACACS+ for authentication and authorization.

6. Extensible Attributes: TACACS+ allows for extensible attributes to be passed during the authentication and authorization process. This feature enables administrators to exchange additional information between the client and server, providing more flexibility for implementing custom features.

7. Device Administration vs. Dial-in Access: Historically, RADIUS was designed for dial-in access scenarios (e.g., remote user access to the network via modems). While it has been extended to support other use cases, TACACS+ was specifically designed for device administration, making it a more suitable choice for network equipment login scenarios.

In summary, TACACS+ is often preferred over RADIUS for network equipment login when the organization requires fine-grained access control, enhanced security, comprehensive accounting, and native vendor support for Cisco devices. However, it's essential to evaluate the specific needs and infrastructure of the organization before making a final decision, as both protocols have their merits and can be suitable for different network environments.