- Products
- Learn
- Local User Groups
- Partners
- More
AI Security Masters E7:
How CPR Broke ChatGPT's Isolation and What It Means for You
Blueprint Architecture for Securing
The AI Factory & AI Data Center
Call For Papers
Your Expertise. Our Stage
Good, Better, Best:
Prioritizing Defenses Against Credential Abuse
Ink Dragon: A Major Nation-State Campaign
Watch HereCheckMates Go:
CheckMates Fest
Dear Community,
I have security gateway 9000 series with 81.20 version. Our users authenticating to remote access VPN via SAML (Entra ID).
Auth works fine, but we facing problem with Access Roles and policies. I can see source user in logs but traffic didin't match to rule with access role where user account is present.
We have policies with Access Role and in this object are user form Entra ID.
In Entra we have two applications, first from gallery "Checkpoint Remote Secure Access VPN" for SAML auth, second custom APP used as Azure AD object in SMS.
Main problem is situation where we have rule with access role and this access role have user account form Azure AD, but traffic from user didin't hit expected rule and goes to clean up rule.
To integrate Remote Access VPN and Entra ID throught SAML we followed this video https://www.youtube.com/watch?v=yZVB3sJ3fZ8
We done almost everything form this post https://community.checkpoint.com/t5/General-Topics/Remote-Access-VPN-and-EntraID-Group-Authorization...
In one access role we have one user, but in feature we will be adding groups. In logs i can see source user in format name@domain
Does anyone know what the potential problem could be ?
Access Roles are calculated based on groups the user is a part of.
For on-premise AD, they are fetched via LDAP.
For EntraID, they are passed as part of the SAML assertion and the gateway must be configured to recognize them.
If there are no groups, then the role is calculated as "All Users."
Which means you cannot allow access to only a single user UNLESS they are a member of a group that only contains them as a member.
Are you able to attach a screenshot of the rule? Please blur out any sensitive data.
Hi,
screenshots od rule and acces role is below
Are there any hits on that rule at all?
Not now, hits was when i don't have access role with user form AD in source. This is main problem. I successfuly auth to VPN via SAML, but traffic don't hit my rule.
Do you see anything when you run pdp monitor user and then that username? If not, then thats your issue. However, if you do see results, maybe try disable rule, install policy-re-enable, install again, test.
Below output drom pdp command executed on firewall
I tried your suggestion but without effect. In my opinion user in access role is not mapping to user from VPN authentication. But i don't know why.
I think I know why. I saw somewhere name has to start with ext and that is a requirement. let me see if I can find it.
@Jakub132620 Sorry my bad, name does not have to start with that, but it seems it should match with what you have on Azure side, so can you give it same name that starts with aad?
How can i check this ?
In Entra i can see the same user.principalname as in on-prem AD
In SmartConsole, create an internal User Group object with this name (case-sensitive, spaces not supported):
EXT_ID_<Name_of_Role>
For example, for a role in the Identity Provider's interface with the name my_group, create an internal User Group object in SmartConsole with the name EXT_ID_my_group.
Right, I recall seeing that, but cant find official documentation where it states to do so...
Just spoke with a colleague and he said thats how he did it for a customer and it did work, was not in any doc nesessarily.
What is the Access Role referring to here, a specific user?
Yes, currently in Access Role i want add signle user form Entra. Is it possible ?
Access Roles are calculated based on groups the user is a part of.
For on-premise AD, they are fetched via LDAP.
For EntraID, they are passed as part of the SAML assertion and the gateway must be configured to recognize them.
If there are no groups, then the role is calculated as "All Users."
Which means you cannot allow access to only a single user UNLESS they are a member of a group that only contains them as a member.
Thats it, you got it! I actually went through my notes I had about it and saw my colleague wrote a doc indicating the same, even if its single user.
Are you utilising on-prem AD as well or pure Entra?
Hi we using on-perm AD and Entra ID
Also, make sure to follow these:
I read the article you linked to. However, there's one point I don't understand. In the "Configuration in Microsoft Azure Portal" section, we create a custom application for downloading users.
My application was created according to point 1. However, I'm having trouble with point 2.
When I go to the Single Sign-ON tab in my application and select SAML, I can't select specific claims because the first step in the application requires configuring the Basic SAML configuration section. I configured the Basic SAML configuration section in the Checkpoint Remote Secure Access VPN application from the gallery, which is used for VPN authentication via SAML.
Mind pasting part you are referring to?
Configuring SAML as a Single Sign-On for your Azure application
Click on Home and select Azure Active Directory from the menu.
Click on Enterprise applications and go to All applications.
Select your application.
The application Overview window opens.
Click Single Sign-On.
Select SAML as the Single Sign-On method.
In the Set up Sign-On with SAML window, go to the User Attributes & Claims section and click the pencil icon to edit the claims.
The User Attributes & Claims window opens.
In the Required claim section, click Unique User Identifier (Name ID).
In the Manage claim window:
Attribute option - Select.
Source Attribute drop-down menu - Select user.localuserprincipalname.
Click Save to save the user claims, then close the window.
Back on the SAML Signing Certificate page, go to the Federation Metadata XML file and click Download.
The Federation Metadata XML is downloaded.
I can't set the appropriate claim because, as I wrote above, the first step in the application requires configuring the Basic SAML configuration section. I configured the Basic SAML configuration section in the Checkpoint Remote Secure Access VPN application from the gallery, which is used for VPN authentication via SAML.
I see. That link is what we always give to customers if there is an issue, though we help them with the setup. Might be worth opening TAC case then.
cluster object > vpn client > authentication > Multiple Auth client settings > Edit the IDP object > User Directories > can you confirm the settings there ?
is External user profiles enabled ?
Also, under Identity awareness is Remote Access checked in ?
1 ) Claim config in Checkpoint VPN application
2) Options in authentication
3) Identity Options
are you able to enable LDAP users, all gateway or specific and Ldap lookup type to User-principal-Name/UPN (UserPrincipalName)
We changed our settings. But it didn't help
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
Tue 28 Apr 2026 @ 06:00 PM (IDT)
Under the Hood: Securing your GenAI-enabled Web Applications with Check Point WAFThu 30 Apr 2026 @ 03:00 PM (PDT)
Hillsboro, OR: Securing The AI Transformation and Exposure ManagementTue 28 Apr 2026 @ 06:00 PM (IDT)
Under the Hood: Securing your GenAI-enabled Web Applications with Check Point WAFTue 12 May 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point Cloud Firewall delivered as a serviceThu 30 Apr 2026 @ 03:00 PM (PDT)
Hillsboro, OR: Securing The AI Transformation and Exposure ManagementAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY