# Client role wildcard

**URL:** <https://forum.inductiveautomation.com/t/client-role-wildcard/19903>\
**Category:** Ignition\
**Created:** [October 1, 2018, 8:45am UTC](https://forum.inductiveautomation.com/t/client-role-wildcard/19903 "2018-10-01T08:45:10Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Claus\_Nielsen](https://avatars.discourse-cdn.com/v4/letter/c/77aa72/32.png) [@Claus\_Nielsen](https://forum.inductiveautomation.com/u/Claus_Nielsen)\
**Post date:** [October 1, 2018, 8:45am UTC](https://forum.inductiveautomation.com/t/client-role-wildcard/19903/1 "2018-10-01T08:45:10Z")

</div>

Is there any secret wildcard I can’t find in the docs that can be used when setting a projects required client roles?  
e.g. ‘SomeStaticRolePrefix\_%’

---

<div class="post-metadata">

**Author:** ![ryanjmclaughlin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryanjmclaughlin/32/4318_2.png) [@ryanjmclaughlin](https://forum.inductiveautomation.com/u/ryanjmclaughlin)\
**Post date:** [October 1, 2018, 11:57am UTC](https://forum.inductiveautomation.com/t/client-role-wildcard/19903/2 "2018-10-01T11:57:58Z")

</div>

For the Project roles, I don’t think a wild card is possible AFAIK. I have always put the list of roles in a CSV list in that field.

---

<div class="post-metadata">

**Author:** ![Claus\_Nielsen](https://avatars.discourse-cdn.com/v4/letter/c/77aa72/32.png) [@Claus\_Nielsen](https://forum.inductiveautomation.com/u/Claus_Nielsen)\
**Post date:** [October 1, 2018, 1:41pm UTC](https://forum.inductiveautomation.com/t/client-role-wildcard/19903/3 "2018-10-01T13:41:30Z")

</div>

> [@ryanjmclaughlin](#):
>
> I have always put the list of roles in a CSV list in that field

You mean the comma seprated textfield? Or am I missing some other way of setting the project roles?

---

<div class="post-metadata">

**Author:** ![ryanjmclaughlin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryanjmclaughlin/32/4318_2.png) [@ryanjmclaughlin](https://forum.inductiveautomation.com/u/ryanjmclaughlin)\
**Post date:** [October 1, 2018, 1:50pm UTC](https://forum.inductiveautomation.com/t/client-role-wildcard/19903/4 "2018-10-01T13:50:48Z")

</div>

> [@Claus\_Nielsen](#):
>
> You mean the comma seprated textfield?

Yes

[https://docs.inductiveautomation.com/display/DOC79/Login+Security](https://docs.inductiveautomation.com/display/DOC79/Login+Security)

---

<div class="post-metadata">

**Author:** ![Claus\_Nielsen](https://avatars.discourse-cdn.com/v4/letter/c/77aa72/32.png) [@Claus\_Nielsen](https://forum.inductiveautomation.com/u/Claus_Nielsen)\
**Post date:** [October 1, 2018, 1:52pm UTC](https://forum.inductiveautomation.com/t/client-role-wildcard/19903/5 "2018-10-01T13:52:42Z")

</div>

That is where I wanted to put wildcards in the first place 🙂

---

<div class="post-metadata">

**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\
**Post date:** [October 1, 2018, 2:32pm UTC](https://forum.inductiveautomation.com/t/client-role-wildcard/19903/6 "2018-10-01T14:32:31Z")

</div>

For client zones and roles we do a case-insensitive check of the entire role – wild cards aren’t possible.

---

<div class="post-metadata">

**Author:** ![Claus\_Nielsen](https://avatars.discourse-cdn.com/v4/letter/c/77aa72/32.png) [@Claus\_Nielsen](https://forum.inductiveautomation.com/u/Claus_Nielsen)\
**Post date:** [October 1, 2018, 2:47pm UTC](https://forum.inductiveautomation.com/t/client-role-wildcard/19903/7 "2018-10-01T14:47:46Z")

</div>

No worries, changed the user source to a database and I now manage the roles from there. A view is managing the wildcards using a role/project based system where assigning a user to a role within a project (Also a db table) also grants a generated role for the user prefixed with “\_\_” e.g. granting a user the role “SomeRole” within project “ProjectName” also grants the role “\_\_ProjectName” to the user.

Now the client roles is limited to “AutoLogin, \_\_ProjectName”