I have successfully configure a Windows 2008 NPS (radius) server to authenticate users when loggin into a test router, I used this link http://aaronwalrath.wordpress.com/2010/06/22/install-windows-2008-r2-nps-for-radius-authentication-for-cisco-router-logins/
Anyway this gives users level 15 priv and they need to access the enable password to edit. How can I get it so I have 2 groups, admins and read only users, so when the admin logs in they have full rights and if the read only users log in they can only view the config and not make any changes?
The trick is that you have to give the level of access per group. Each group should have their own Connection Request Policy and Network Policy which in the end will determine the access level.
By using the Vendor attribute: Cisco-AV-Pair shell:priv-lvl=15, you are giving that group level 15 access.
So you have to change yours accordingly:
I have my own blog with this set up on:
Hope it helps.
I'm just stuck on the last part of you tutorial:
line vty 0 4
login authentication vty <<<------- Make sure this is the same as in the aaa authentication login
1.) What should it be?
2.) How can I set up a policy to give a user just read only permission to the CLI?
What I meant is tht whatever you put on this line has to be the same as in the parameter you set on this aaa line:
aaa authentication login vty group radius local-case [ this is case sensitive]. if you have VTY then on they should be the same on both lines.
The users' login access is controlled on the NPS.
The Vendor specific attribute controls that part.
shell:priv-lvl=15 gives the Level 15
privilege level 1 = non-privileged (prompt is router>), the default level for logging in
privilege level 15 = privileged (prompt is router#), the level after going into enable mode
privilege level 0 = seldom used, but includes 5 commands: disable, enable, exit, help, and logout
So you choose the one you want.
There are also ways to assigning commands that can be used using the AAA templates and such so let me know what else you need.
What is Connection Request Policy used for as I put the IP on my PC in to give it access and it worked, but it also works if I disable it?
Connection request policies are sets of conditions and settings that allow network administrators to designate which RADIUS servers perform the authentication and authorization of connection requests that the server running NPS receives from RADIUS clients.
see: http://technet.microsoft.com/en-us/library/cc753603.aspx for more.
So is it possibel to give users in one Windows Active Directoty group priv 15 access and another group say Priv 3 access but we can define the commands they need?
See this documentation:
Thanks, but what I don't understand is where this custom priv access gets configured on your radius instructions. I can get level 15 working, but for this second group what do I need to do, as I need 2 types of users?
You need to specify different policies for the two groups.
If on your AD, you have network admins, and helpdesk, you need to specify them in step 10 on network policy.
You can have the same connection policy for both and then a different network policy for each group. the access level will be determined by the group and the VA specified on shell:priv-lvl=15 [network admins] or shell:priv-lvl=7 [for helpdesk] attribute on each of the Network policies.
Hope still someone is following this tread.
I have done the conf Mandlenkosi Nkiwane suggested:
but than when i try to authenticate with the user in the group i always get the level15
*Aug 16 16:57:31.395: AAA/BIND(0000148F): Bind i/f
*Aug 16 16:57:35.199: AAA/AUTHOR/EXEC(0000148F): processing AV priv-lvl=1
*Aug 16 16:57:35.199: AAA/AUTHOR/EXEC(0000148F): processing AV priv-lvl=15
*Aug 16 16:57:35.199: AAA/AUTHOR/EXEC(0000148F): processing AV service-type=6
*Aug 16 16:57:35.199: AAA/AUTHOR/EXEC(0000148F): Authorization successful
*Aug 16 16:57:46.427: AAA/BIND(00001490): Bind i/f
When I configure this I always configure authorization on the vty line specifically. So for instance:
aaa new-model aaa group server radius RADIUS_SERVERS server name RADIUS01 aaa authentication login VTY local group RADIUS_SERVERS aaa authorization exec VTY local group RADIUS_SERVERS radius server RADIUS01 address ipv4 192.168.1.2 auth-port 1645 acct-port 1646 key 0 radiuskey line vty 0 4authorization exec VTY <-- this seems to get the av-pair info and apply it to the sessionlogin authentication VTY
transport input ssh
I wrote an article on this and have it posted here if you need more details: