# Roles containing backshashes cannot be mapped to level groups

**URL:** <https://forum.inductiveautomation.com/t/roles-containing-backshashes-cannot-be-mapped-to-level-groups/91307>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [June 3, 2024, 7:23pm UTC](https://forum.inductiveautomation.com/t/roles-containing-backshashes-cannot-be-mapped-to-level-groups/91307 "2024-06-03T19:23:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![diamond](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@diamond](https://forum.inductiveautomation.com/u/diamond)\
**Post date:** [June 3, 2024, 7:23pm UTC](https://forum.inductiveautomation.com/t/roles-containing-backshashes-cannot-be-mapped-to-level-groups/91307/1 "2024-06-03T19:23:49Z")

</div>

Hello

I have been struggling all the afternoon to map the AD Groups returned by my SAML provider to Ignition level groups. It turns out that there is a bug in Ignition where a role containing a backlash cannot be mapped using `containsAny` or `containsAll`.

> containsAny({user:roles}, 'domain\AD\_Group')

This is important because `Microsoft's AD groups` are returned in the following format: "domain\AD\_Group\_Name".

You can check it with any provider, and see that this happens even with the traditional authentication.

Ignition version: **8.1.41**

Thanks!!

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 3, 2024, 7:44pm UTC](https://forum.inductiveautomation.com/t/roles-containing-backshashes-cannot-be-mapped-to-level-groups/91307/2 "2024-06-03T19:44:47Z")

</div>

Does a doubled backslash work?

---

<div class="post-metadata">

**Author:** ![diamond](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@diamond](https://forum.inductiveautomation.com/u/diamond)\
**Post date:** [June 3, 2024, 7:59pm UTC](https://forum.inductiveautomation.com/t/roles-containing-backshashes-cannot-be-mapped-to-level-groups/91307/3 "2024-06-03T19:59:52Z")

</div>

Good one, it works!

> containsAny({user:roles}, 'domain\\AD\_Group')

Should I consider this a temporary fix or a permanent solution?

Thanks @paul-griffith

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 3, 2024, 8:31pm UTC](https://forum.inductiveautomation.com/t/roles-containing-backshashes-cannot-be-mapped-to-level-groups/91307/4 "2024-06-03T20:31:34Z")

</div>

A permanent solution. Backslashes are how the expression language (and many other programming contexts...) distinguish special characters in strings, like `\r`, `\t`, etc. Doubled backslashes is effectively cancelling the escape sequence from the first backslash to emit a single literal backslash in the output string.
