- Products
- Learn
- Local User Groups
- Partners
- More
Quantum Spark Management Unleashed!
Check Point Named Leader
2025 Gartner® Magic Quadrant™ for Hybrid Mesh Firewall
HTTPS Inspection
Help us to understand your needs better
CheckMates Go:
SharePoint CVEs and More!
Hello folks,
I have integrated Active directory with Checkpoint R80.10. So can I use the active directory user log in for smart console. I do not have radius server. Please let me know Is it possible and how?
Hi Blason R, I actually had implemented the option told by Norbert Bohusch in my environment:
a Windows Server with the NPS role installed on a separate server of the domain controller (I believe putting the NPS in a DC is a big NO-NO).
Also as Norbert says the NPS role is essentially a Radius server, so you have to follow the instructions for "Configuring a RADIUS Server for Administrators" from the Admin Guide:
- Create a Radius Server object with a shared secret on the SmartConsole
- In the NPS server create a Radius Client with the Management/SmartCenter IP address and obviously the same shared secret from above
- Create a Connection Policy with at least a condition (for example the NAS IPv4 address as the IP address of mgmt) with EAP-MSCHAP as authentication method
- Create a Network Policy with also at least the same condition above (but I also configure a condition for the users must be members of an specific AD group)
- Create an administrator on the SmartConsole with a username format like <AD domain>\<AD user> and Radius as authentication method
Then you can login using the <AD domain>\<AD user> as user name and your AD password as password.
Hope it helped
I just recently became aware of this SK that provides a mechanism for authenticating SmartConsole users with Active Directory.
It is supported from R80.20 JHF, but has some limitations, and thus won't be appropriate in every situation.
See: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...
Hi Blason R, I actually had implemented the option told by Norbert Bohusch in my environment:
a Windows Server with the NPS role installed on a separate server of the domain controller (I believe putting the NPS in a DC is a big NO-NO).
Also as Norbert says the NPS role is essentially a Radius server, so you have to follow the instructions for "Configuring a RADIUS Server for Administrators" from the Admin Guide:
- Create a Radius Server object with a shared secret on the SmartConsole
- In the NPS server create a Radius Client with the Management/SmartCenter IP address and obviously the same shared secret from above
- Create a Connection Policy with at least a condition (for example the NAS IPv4 address as the IP address of mgmt) with EAP-MSCHAP as authentication method
- Create a Network Policy with also at least the same condition above (but I also configure a condition for the users must be members of an specific AD group)
- Create an administrator on the SmartConsole with a username format like <AD domain>\<AD user> and Radius as authentication method
Then you can login using the <AD domain>\<AD user> as user name and your AD password as password.
Hope it helped
Still not possible the way you want to do it.
See the documentation R80.10 Management Admin Guide, Section: Configuring Authentication Methods for Administrators
Same goes for R80.20 Management Admin Guide, Section: Configuring Authentication Methods for Administrators
I did hear that request/question from every customer who was thinking about moving away from local OS accounts. And it is the first question that comes to mind, always.
I do struggle to understand this approach, however. I reckon that there is a very good reason behind this, though. I'm sure. 100%. No doubt.
Could someone knowing(!) the reasons please elabotrate about this?
Maybe it is about, who has control over the authorizing system and it's security measures and options (2FA, etc.)
For reference this has been discussed previously in another thread, see here:
I just recently became aware of this SK that provides a mechanism for authenticating SmartConsole users with Active Directory.
It is supported from R80.20 JHF, but has some limitations, and thus won't be appropriate in every situation.
See: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...
To bring back an old post again, in R81 and R81.10 there seems to be a difference in the Kerberos part used underwater. Due to company policies we were forced to harden the AD server and ran into an issue when the following encryption types were disabled for the Kerberos authentication:
DES_CBC_CRC, DES_CBC_MD5, RC4_HMAC_MD5
Then we found that authentication to a R81 MDS was no longer working in a capture you see Kerberos errors with preauth_required, response_too_big and etype_nosupp
At the same time authenticating to a R81.10 MDS worked just fine, so it seems to be a version related.
Main question here: is there a way to force higher encryption types on the kerberos protocol?
Perhaps you already solved it, but this link looks to be the solution
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
19 | |
7 | |
6 | |
5 | |
4 | |
4 | |
4 | |
2 | |
2 | |
2 |
Fri 12 Sep 2025 @ 10:00 AM (CEST)
CheckMates Live Netherlands - Sessie 38: Harmony Email & CollaborationTue 16 Sep 2025 @ 02:00 PM (EDT)
Securing Applications with Check Point and AWS: A Unified WAF-as-a-Service Approach - AmericasWed 17 Sep 2025 @ 04:00 PM (AEST)
Securing Applications with Check Point and AWS: A Unified WAF-as-a-Service Approach - APACWed 17 Sep 2025 @ 03:00 PM (CEST)
Securing Applications with Check Point and AWS: A Unified WAF-as-a-Service Approach - EMEAThu 18 Sep 2025 @ 03:00 PM (CEST)
Bridge the Unmanaged Device Gap with Enterprise Browser - EMEAFri 12 Sep 2025 @ 10:00 AM (CEST)
CheckMates Live Netherlands - Sessie 38: Harmony Email & CollaborationTue 16 Sep 2025 @ 02:00 PM (EDT)
Securing Applications with Check Point and AWS: A Unified WAF-as-a-Service Approach - AmericasWed 17 Sep 2025 @ 04:00 PM (AEST)
Securing Applications with Check Point and AWS: A Unified WAF-as-a-Service Approach - APACWed 17 Sep 2025 @ 03:00 PM (CEST)
Securing Applications with Check Point and AWS: A Unified WAF-as-a-Service Approach - EMEAThu 18 Sep 2025 @ 03:00 PM (CEST)
Bridge the Unmanaged Device Gap with Enterprise Browser - EMEAAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY