12-18-2023 07:17 AM
Hi,
I`m trying to understand what is missing.
I Configured in my switch to authenticate and authorize VTY connections via Radius servers.
The console connection I left to be authenticated and authorized using Local credentials.
the command are:
12-18-2023 07:23 AM
I dont like config any AAA under console' console is your last hope if you can not access to SW via vty.
Config it with AAA and there is issue in connect to AAA can make you never access to SW via console.
But if you want go that way
Check
aaa authorization console <- I think there is conflict between it and aaa authorization exec
MHM
12-18-2023 08:08 AM
First dont WR NEVER when you do any change to aaa' in case that something wrong you can reboot and return to old config.
Now use different method dont use defualt for console auth and authz
Try and check
MHM
12-18-2023 07:38 AM - edited 12-18-2023 07:39 AM
Hello @itzikk
Add this
aaa authorization console local
12-19-2023 02:36 AM
Hello
Append the following:
username xxx privilege 15 secret ccc
aaa authentication login default local
aaa authorization exec default local if-authenticated
12-19-2023 07:57 AM
Thanks all,
Unfortunately, it`s not resolving the issue.
What i`m trying to make is that my VTY connections will be authenticated via Radius servers directly into Privileged exec mode. On the same time, i want my Console connection to authenticate using local credentials.
I manage to login the VTY lines directly into Privileged exec mode by using the command: aaa authorization exec aaa-auth group radius-verify local
By default, line con 0 is not using authorization, so i assumed it will connect without authorization, but i did get "Authorization Failed". That`s why i configured aaa authentication login default local if-authenticated, But still got the same error of Authorization Failed.
I noticed that when I write under the VTY lines "no authorization exec aaa-auth", I login into User exec mode, and when i try with my console line i`m able to login with no error.
Conclusion: for some reason, as long as i use aaa named method of authorization under VTY lines, it is affecting the Console line also, although the the console by default shouldnt be affected by the aaa authorization.
Any thoughts?
12-19-2023 08:04 AM
Same config you share in your original post
Clear line vty all
Then try only access to console
Maybe us same username in to vty and console effect the authz
MHM
12-19-2023 08:12 AM
The only difference between line vty now and con 0 is that line vty uses named authentication list forwarding to Radius group, and the console uses the default one using local credentials.
The aaa authorization is:
aaa authorization exec default local if-authenticated
Im able to connect on both VTY and Console lines.
But, in VTY im connecting only to User mode, and i want to connect directly into Privileged mode.
The moment i configure named authorization forwarding to radius, and configure it under VTY, im getting Error in the console login "Authorization Failed"
12-19-2023 09:37 AM
I will do some test to check.
Update you soon
MHM
01-08-2024 06:50 AM
As i find out, there is a bug in my Switch and thats the reason it wasn`t working well.
Tried in another switch and worked fine.
thanks
01-08-2024 06:52 AM
Thanks alot for update us
Can yoh share the bug id
Thanks again
MHM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide