> Source: [sk183250](https://support.checkpoint.com/results/sk/sk183250)

# sk183250 - Remote Access VPN with SAML Does Not Enforce Access Roles for Azure AD Users/Groups

| Property | Value |
|----------|-------|
| Solution ID | sk183250 |
| Date Created | 2025-03-20 |
| Last Modified | 2025-03-25 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82, R81.20, R81.10 (EOS) |

## Symptoms

- * After successful SAML authentication and VPN connection, internal resources remain inaccessible via Access Role.

* Running the command `"# pdp m a on"` on the Security Gateway when the Remote Access VPN client is connected does not display any assigned groups.

* Remote Access VPN users only match Access Roles with 'any user' and, in some cases, groups prefixed with `EXT_ID_`, granting them access to internal resources.

## Cause

The Azure Single Sign-On (SSO) configuration for SAML uses an incorrect Unique User Identifier.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content