06-21-2023 05:42 PM
In IOS-XE, there is a command that allows you to encrypt the TACACS+ and RADIUS keys to Type 6 so you don't get the annoying alert about using deprecated password types. When I worked on a C1000 today (which is not using IOS-XE), I did not see the commands to allow for entering the encryption key:
Switch(config)# password encryption aes
Switch(config)# key config-key password-encrypt
Is there some other way of encrypting the TACACS/RADIUS passwords on the C1000?
Model: Catalyst 1000-24P-4G-L
Firmware: 15.2.7E6(MD) - released 29-Sep-2022
06-28-2023 08:17 AM
Device(config-radius-server)# key 6 cisco123
06-28-2023 05:20 PM
That is not how that command works. When you specify the number 6 after the word "key", you must enter a password that is already encrypted using the type 6 encryption.
C3560-CX-CORE(config-radius-server)#key ?
0 Specifies an UNENCRYPTED key will follow
6 Specifies ENCRYPTED key will follow
7 Specifies HIDDEN key will follow
LINE The UNCRYPTED (cleartext) shared key
If you try to enter "cisco123" as you have in your example, you will get an error:
C3560-CX-CORE(config-radius-server)#key 6 cisco123
Invalid type-6 encrypted password: cisco123
% Invalid encrypted key: cisco123
It appears that you have to encrypt the password on a device that does allow you to encrypt the passwords and then paste the result into the C1000 config. It's a shame that this model doesn't allow you to do it natively "on the box"
06-28-2023 05:26 PM
You are totally right' I already run lab to check this case I will update you when find solution.
Thanks
MHM
02-01-2024 03:34 AM
Has anyone found a solution to this issue? I am struggeling with the same problem.
02-01-2024 06:52 AM
Romel, hopefully you have higher end switches available. The only solution I see is to:
Disclaimer: I have not tried this as I don't have the hardware available to me at this time to test this thoroughly but anyone else that can test this, I would love to get your feedback as to if this works.
02-16-2024 02:18 AM
Hello,
I tried that approach and it doesn't work. It throws an error stating the encrypted key is not valid.
I assume that, since you haven't defined the passphrase to create such encryption, the system is not able to understand the encrypted password. If there's a hardcoded passphrase that encrypts type 6, this approach might work if we used that key.
BR,
02-21-2024 10:11 AM
Hello,
The command password encryption aes is not available on C1000 platform because the symmetric AES keys are not supported.
The device supports the Advanced Encryption Standard (AES) encryption algorithm with a 128-bit key, 192-bit key, or 256-bit key. However, symmetric cipher AES to encrypt the keys is not supported.
I have the same issue with that log message
"WARNING: Command has been added to the configuration using a type 0 password. However, type 0 passwords will soon be deprecated. Migrate to a supported password type"
Regards Kamil
05-27-2024 07:19 PM
Hi, as long as you have "password encryption aes" configured , when you configure your tacacs key, you can use key 0 or 7, and it should be updated by the router with key 6 as long as AES is working ( you need to also set the encryption key that the router will use to encrypt your clear txt passwords with, key config-key password encrypt <password>)
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