# Ignition is continously accessing user database

**URL:** <https://forum.inductiveautomation.com/t/ignition-is-continously-accessing-user-database/58409>\
**Category:** Ignition\
**Created:** [April 13, 2022, 11:58am UTC](https://forum.inductiveautomation.com/t/ignition-is-continously-accessing-user-database/58409 "2022-04-13T11:58:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\
**Post date:** [April 13, 2022, 11:58am UTC](https://forum.inductiveautomation.com/t/ignition-is-continously-accessing-user-database/58409/1 "2022-04-13T11:58:48Z")

</div>

I’m using AD/Database Hybrid Authentication in Ignition 8. There is also an Indentity Provider using that Usersource.  
The database access log shows that Ignition is continously reading the ‘User’s Roles Query’. There is about one query per second, cycling through all user names and then starting again.  
Has anybody an idea what causes that queries? I have enabled all possible loggers without success. Our IT department wants this query flooding to stop or at least an explanation why it is happening.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 13, 2022, 12:03pm UTC](https://forum.inductiveautomation.com/t/ignition-is-continously-accessing-user-database/58409/2 "2022-04-13T12:03:51Z")

</div>

Seems like this query is run often… during badge or username/pass authentication, user creation, getting a user or users from scripting…

---

<div class="post-metadata">

**Author:** ![peter](https://avatars.discourse-cdn.com/v4/letter/p/278dde/32.png) [@peter](https://forum.inductiveautomation.com/u/peter)\
**Post date:** [April 13, 2022, 1:01pm UTC](https://forum.inductiveautomation.com/t/ignition-is-continously-accessing-user-database/58409/3 "2022-04-13T13:01:16Z")

</div>

How many users do you have, and is it obviously cycling through in a linear fashion? @Kevin.Herron suggests that the query will be executed a lot due to the mechanics of Ignition, but I would expect a more random pattern if that was the case. And is it cycling through users that are not logged in?

---

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [April 13, 2022, 1:04pm UTC](https://forum.inductiveautomation.com/t/ignition-is-continously-accessing-user-database/58409/4 "2022-04-13T13:04:03Z")

</div>

Are you calling [system.user.getRoles - Ignition User Manual 8.0 - Ignition Documentation](https://docs.inductiveautomation.com/display/DOC80/system.user.getRoles) or any other system.user.\* scripts in a timer script?

---

<div class="post-metadata">

**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\
**Post date:** [April 13, 2022, 5:36pm UTC](https://forum.inductiveautomation.com/t/ignition-is-continously-accessing-user-database/58409/5 "2022-04-13T17:36:57Z")

</div>

What is your `Cache Validation Timeout` set to on the AD / DB Hybrid user source profile’s config settings?

---

<div class="post-metadata">

**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\
**Post date:** [April 14, 2022, 11:49am UTC](https://forum.inductiveautomation.com/t/ignition-is-continously-accessing-user-database/58409/6 "2022-04-14T11:49:17Z")

</div>

Thank you for all the input. The queries seem to be caused by the 60 second `Cache Validation Timeout` For an unknown reason, each query takes about 2 seconds to complete, so a single validation cycle takes longer than 60 seconds.  
IT is now investigating the MySql server to find out why this simple query takes so long.
