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

# sk166199 - Some Access Control policy rules with Access Role objects are not matched when the nested groups state is set to 2

| Property | Value |
|----------|-------|
| Solution ID | sk166199 |
| Date Created | 2020-04-06 |
| Last Modified | 2021-03-01 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R81 (EOS) |
| OS | Gaia |

## Symptoms

- * Some Access Control policy rules with Access Role objects are not matched.

* The command "`pdp monitor user <UserName>`" on the Identity Awareness Gateway shows that direct groups are fetched correctly, but nested groups are not fetched.

* The command "`pdp nested_groups status`" on the Identity Awareness Gateway shows "*Enabled - mode 2*".

* The Identity Awareness Gateway sends the LDAP query to the LDAP server to the TCP port 389 or 636.

* The PDP Debug (`pdp debug set all all`) on the Identity Awareness Gateway shows an empty "`dn =`":  

  `[RootId = XXX] server = XXX, Search[ dn = '', Params[ scope = 2, filter = '(&(objectCategory=group)`  
  `(member:XXX:=CN=XXX,CN=XXX,DC=XXX,DC=XXX) )'`

## Cause

When the query is done over the TCP port 389 or 636, the LDAP server expects to receive a base Distinguished Name. The Identity Awareness Gateway does not send it.

## Solution

This problem was fixed. A new nested groups mode configuration was added.

The new nested groups mode:

* Supports LDAP Account Unit with one branch that is connected to one Active Directory domain tree.
* Supports all LDAP ports (3268 or 3269, 389 or 636).

Even if previously you installed a hotfix for this issue, and then you install the Jumbo Hotfix Accumulator listed below, you must run the command below immediately to get the new behavior:

1. Connect to the command line on the Security Gateway (each Cluster Member).
2. Log in to the Expert mode.
3. Configure the nested groups state to 4:  
   `pdp nested_groups __set_state 4`

The fix is included in:

* [Check Point R81](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk166715)
* [Jumbo Hotfix Accumulator for R80.40](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk165456) starting from Take 91
* [Jumbo Hotfix Accumulator for R80.30](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk153152) starting from Take 227
* [Jumbo Hotfix Accumulator for R80.20](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk137592) starting from Take 190
* [Jumbo Hotfix Accumulator for R80.10](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk116380) starting from Take 288

If you choose not to upgrade, Check Point can supply a **Hotfix** . [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.  
A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.  
For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk168597).

<br />

**Workaround**: Enable Global Catalog on the applicable LDAP server and move the Account Unit listening port to 3268 or 3269.

---

# 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