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

# sk131872 - AD users with special characters in their names cannot authenticate

| Property | Value |
|----------|-------|
| Solution ID | sk131872 |
| Date Created | 2018-07-15 |
| Last Modified | 2022-02-21 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- AD users with special characters (for example a comma) in their names cannot authenticate.

## Solution

This problem was fixed. The fix is included in:

* [Check Point R80.30](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk144293)
* [Jumbo Hotfix Accumulator for R80.10 (R80_10_jumbo_hf)](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk116380) from Take 142

In addition to installing the new Take, to be able to login with a user name that contains special characters, edit the *identity_awarness_custom_settings.C* file on the Security Management Server.

These adjustments in *identity_awarness_custom_settings.C* are always required, even no hotfix is needed for a specific release.

In case the environment is an "MDS", please verify that we're in the proper CMA as follows:

#mdsenv \<desired CMA\>

#mcd

Then, perform the below procedure.

1. Backup the *$FWDIR/conf/identity_awareness_custom_settings.C* file
2. Edit the "*user_at_domain_whitelist* " section so that it will contain the desired special characters.

   This is the format of the file:

   *\[user_at_domain_whitelist\]*

   *#In this section you can add special escape chars to be whitelisted not as domain marker ('\\')*   
   *#Each special sequence should be written in new line*   
   *#e.g.*   
   *#\\,*   
   *#\\.*   
   *#And then you can log in for example with the user: CN=John\\,Doe\\.,OU=Users,DC=domain,DC=com*

   *\[/user_at_domain_whitelist\]*
   * If this section is missing on your Security Management gateway (which can happen after a version upgrade for example), copy the section from above to the end of the file and make changes according to the instructions. Then, save the file and install the Security policy.  

   * If the section exists on your Security Management gateway, edit it to contain all the relevant characters, save the file and install the Security policy.

Check Point recommends to always upgrade to the most recent version ([upgrade Security Gateway](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=downloads&product=435) / [upgrade Cluster](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=downloads&product=428) / [upgrade Security Management Server](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=downloads&product=184) / [upgrade Multi-Domain Security Management Server](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=downloads&product=166)).

---

# 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