- Products
- Learn
- Local User Groups
- Partners
- More
CheckMates Fifth Birthday
Celebrate with Us!
days
hours
minutes
seconds
Join the CHECKMATES Everywhere Competition
Submit your picture to win!
Check Point Proactive support
Free trial available for 90 Days!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
The 2022 MITRE Engenuity ATT&CK®
Evaluations Results Are In!
Now Available: SmartAwareness Security Training
Training Built to Educate and Engage
MITRE ATT&CK
Inside Check Point products!
CheckFlix!
All Videos In One Space
i have integrated my R80.40 smartoconsole and GWs with CIsco ISE via RADIUS protocol.. facing a weird issue for a single user who is not able to loign to smartconsole citing an error authentication failed.. however same password works for CLI login.
There are other users also configured on the same device but none of them have any issue.. any help is appreicated
Thank you all for the replies.. it turned out RADIUS version 1 was configured for ISE object in Smartconsole which was limiting the password character to 16.. i changed it to v2 and now its working fine
it was a mere coincidence that the one user which was affected was using a 17 letter password XD
Just going by my pure logic here, first thing I would personally check is to make sure that permissions and settings for non working user are same as working ones. Assuming they all have same access, I cant really think of any other reason why this would fail. Is that the only message you see in the logs? If you do say tcpdump of fw monitor for that user's IP address or zdebug on just their usernames, what do you see?
Andy
Check the Permission Profile assigned to the user in question.
Also, when you are referring to CLI, are you referring to a Management CLI or CLISH?
On the user record is their any time or expiry constraint set?
Thank you all for the replies.. it turned out RADIUS version 1 was configured for ISE object in Smartconsole which was limiting the password character to 16.. i changed it to v2 and now its working fine
it was a mere coincidence that the one user which was affected was using a 17 letter password XD
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY