# Custom UserStorageProvider doesn't work after config update

**URL:** <https://forum.keycloak.org/t/custom-userstorageprovider-doesnt-work-after-config-update/22056>\
**Category:** Extending the server\
**Tags:** user-federation\
**Created:** [May 10, 2023, 7:58pm UTC](https://forum.keycloak.org/t/custom-userstorageprovider-doesnt-work-after-config-update/22056 "2023-05-10T19:58:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ricozs](https://yyz2.discourse-cdn.com/free1/user_avatar/forum.keycloak.org/ricozs/32/8540_2.png) [@ricozs](https://forum.keycloak.org/u/ricozs)\
**Post date:** [May 10, 2023, 7:58pm UTC](https://forum.keycloak.org/t/custom-userstorageprovider-doesnt-work-after-config-update/22056/1 "2023-05-10T19:58:18Z")

</div>

Hello,

i’ve started a migration of a custom UserStorageProvider from version 15.0.2 to version 21.1.1 This custom provider uses an external data source to load users. While loading (findByUsername …) the user will be imported to keycloak local storage. (refreshed if already existing) . This works as expected.

After configuration change, (for example: rename the custom user-federation) all users that are linked to this federation are disabled. Additionally it seems that the provider is not working anymore, i tried to debug but nothing happened.

Simple example project: [GitHub - ricozs/keycloak-json-userfederation](https://github.com/ricozs/keycloak-json-userfederation)

Any ideas ?

---

<div class="post-metadata">

**Author:** ![ricozs](https://yyz2.discourse-cdn.com/free1/user_avatar/forum.keycloak.org/ricozs/32/8540_2.png) [@ricozs](https://forum.keycloak.org/u/ricozs)\
**Post date:** [May 11, 2023, 10:59am UTC](https://forum.keycloak.org/t/custom-userstorageprovider-doesnt-work-after-config-update/22056/2 "2023-05-11T10:59:13Z")

</div>

It seems that the provider is deactivated after config update although it is displayed as enabled. Within keycloak database the “enabled” field of the component\_config shows “t” instead of “true”. After disable/enable the provider works again (and the component\_config-\>enabled shows “true”).  
I guess this is a bug.
