# Common User Source for Edge Gateways **URL:** \ **Category:** Ignition\ **Created:** [August 28, 2019, 10:59am UTC](https://forum.inductiveautomation.com/t/common-user-source-for-edge-gateways/27831 "2019-08-28T10:59:24Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![jose.granero](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jose.granero/32/11190_2.png) [@jose.granero](https://forum.inductiveautomation.com/u/jose.granero)\ **Post date:** [August 28, 2019, 10:59am UTC](https://forum.inductiveautomation.com/t/common-user-source-for-edge-gateways/27831/1 "2019-08-28T10:59:24Z")
Hi, I’ve an architecture with 18 panel PCs with Ignition Edge, all of them connected to a central Ignition Gateway on AWS, is it possible to configure the Edge Gateways so that they make use of the same, common and centralized User Source configured in the main Ignition Gateway?. Otherwise, managing 19 differents user sources, for the time being, will be a headache. ---
**Author:** ![AJBerera](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@AJBerera](https://forum.inductiveautomation.com/u/AJBerera)\ **Post date:** [July 25, 2022, 10:26pm UTC](https://forum.inductiveautomation.com/t/common-user-source-for-edge-gateways/27831/2 "2022-07-25T22:26:15Z")
I have also been looking into a way to do this, as it seems the database user source option is not available in edge and I do not know how else to do this. Does anyone think this is an issue with using edge instead of a standard remote gateway? ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [November 1, 2024, 3:07am UTC](https://forum.inductiveautomation.com/t/common-user-source-for-edge-gateways/27831/3 "2024-11-01T03:07:00Z")
Another 2 years later, and I'm pondering this as well... I don't know if it's possible to do this via scripting either to sync the user sources up between central and Edges, as you don't have access to raw passwords... I'm thinking, if you use an internal db user source, you could grab the row in the config.db from Central and copy that to the Edge gateways' config.db... maybe. Unless the decryption key is different between gateways ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 1, 2024, 11:39am UTC](https://forum.inductiveautomation.com/t/common-user-source-for-edge-gateways/27831/4 "2024-11-01T11:39:01Z")
I would think that having many users logging into Edge is not really an Edge use-case. If there are many Edge installs and many admin/designer users, EAM is the answer (to push from dev to prod). ---
**Author:** ![DNice](https://avatars.discourse-cdn.com/v4/letter/d/858c86/32.png) [@DNice](https://forum.inductiveautomation.com/u/DNice)\ **Post date:** [November 1, 2024, 12:01pm UTC](https://forum.inductiveautomation.com/t/common-user-source-for-edge-gateways/27831/5 "2024-11-01T12:01:57Z")
The solution I have put together is using AD authentication (roles and such stored in a central DB) along with a RFID badge reader so operators dont need to remember/continually type in their passwords. To syncronize users on edge devices, I set up a script that executes a [`system.util.sendRequest`](https://docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-util/system-util-sendRequest) to my central server with the edge node identifier as a param. The return is a list of users allowed on that device (with role, badge#, language, etc...). Then I itterate over this returned list and add/update users on the edge device. For my use case, executing this logic (on the edge device) when a user logs out as well as providing a button to manually update the users was good enough ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [November 1, 2024, 1:24pm UTC](https://forum.inductiveautomation.com/t/common-user-source-for-edge-gateways/27831/6 "2024-11-01T13:24:52Z")
> [@pturmel](#): > > EAM is the answer (to push from dev to prod). Can EAM sync up users though? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 1, 2024, 1:38pm UTC](https://forum.inductiveautomation.com/t/common-user-source-for-edge-gateways/27831/7 "2024-11-01T13:38:44Z")
I don't think so. But the point was that you don't need developer access to production Edge. ---
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [November 1, 2024, 1:45pm UTC](https://forum.inductiveautomation.com/t/common-user-source-for-edge-gateways/27831/8 "2024-11-01T13:45:06Z")
You can perhaps use an Identity Provider for the "common user source". Edge can connect to IdP. keycloak can be used for the IdP > **[Keycloak](https://www.keycloak.org/)** > > Keycloak is an open source identity and access management solution Not tested yet... ---
**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\ **Post date:** [November 1, 2024, 5:10pm UTC](https://forum.inductiveautomation.com/t/common-user-source-for-edge-gateways/27831/9 "2024-11-01T17:10:48Z")
Following because I also have multiple Ignition gateways deployed (1 full, 5 edge) that should share the same user pool. If there's a way to do this IA should really have a standard approach with examples in the manual.