Forum Discussion
XINGYU_99486
Nimbostratus
May 22, 2014How to configure TACACS+ on Cisco ACS 5.3 for authenticating administrative users on LTM 11.2.0?
Hello,
I was desperate to get the Tacacs+ working on Cisco ACS for LTM 11.2.0. However I was not be able to find a direct answer.
There is my configuration on LTM ->System -> Users -> Auth...
Lazaro_Pereira_
Nimbostratus
Sep 05, 2014Since I ended up banging my head on a wall for a couple of days on this let me post how I got this configured with an ACS 5.3 server that is already configured for AD Authentication and the F5 with remote roles via TACACS :
ACS 5.3
* Add your F5 Devices with key and give them a device type that is separate from the Cisco gear i.e: Device type:F5-Loadbalancers
* Create an Identity group
* Users and Identity Stores > Identity Groups
* Create Admin Group (provide a name and optionally a description)
* Create Operator Group (as above give it a name and description
Bind the Identity Group to the AD group your Admins reside in
* Access Polices > Default Device admin
* Make sure that the check mark under policy structure has "Group Mapping Checked" if not check it and submit
* Access Polices > Default Device Admin > Group Mapping
* Create Rule for group mapping
* Name: DeviceAdmins
* Checkmark Compound Condition
* Dictionary : AD1 , Attribute: External Group , Value: [the AD group for your admins]
* Click addV
* Identity Group click select and choose the admin identity group you created earlier
* Click OK
**Customize and Create the policy rules to send attributes to the F5**
* Access Policies > Default Device Admins > Authorization
* Click Customize
* under Customize Conditions in the available box find the "Identity Groups" and move it to the selected box
* Under Customize Results make sure that both shell profile and Command sets are in the selected box and Click OK
* Create a Rule for Admins
* Name: your choice
* Conditions - NDG:Device Type : All Device Types:F5-Load-Balancers , Identity Group : DeviceAdmins
* Results - Shell Profile : Click Select
* Click Create in the popup and Create a name , click on the Custom Attributes Tab
* Attribute : F5-LTM-User-Info-1 , Requirement: Mandatory , Attribute Value: Static, in the box below type "adm" <---without quotes!
* Click common Tasks tab on top ad set your default Privilege to 1 and Max to 15 (doesnt do anythign for F5 but thats how I have it) and click submit
* Click OK until you are back at the rule page and your new Shell profile should be there.
* Under Command Sets Select PermitAll
* Click Ok
* Click Save
Configuring the F5
GUI
* System > Users > Remote Role Groups
* Create : name : DeviceAdmins, Line Order: 1,Attribute String: F5-LTM-User-Info-1=adm,Assigned Role: Administrators, Partition: all
* Click Finish
Configure TACACS on F5
* System > Users > Authentication
* click Change and select TACACS+
* add your ACS Server(s)
* add your secret key
* Service Name : ppp
* Protocol Name : ip
Under external user I just set that to "No Access"
Click Finished.
You should be able to login now with your AD account. I hope this helps!
- Amit585731May 13, 2015
Nimbostratus
Hi Lazaro, Thanks this worked. Just wanted to know what if we run vulnerability scanner using tacacs login will that work? I am trying to runn scanner on big ip system and scanner is not able to login.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects