How did you package your extension - as jboss module or regular JAR with jboss-deployment-descriptor.xml ? I did lately similar exercise with 4.8.3 and login forms. You need to modify standalone.xml and set your provider as primary one while disabling default one: <spi name=“account"> <default-provider>my-custom-provider</default-provider> <provider name="my-custom-provider" enabled="true"/> <provider name="freemarker" enabled="false"/> </spi> My extension is packaged as JBoss module and registered via providers configuration: <subsystem xmlns="urn:jboss:domain:keycloak-server:1.1"> <web-context>ROOT</web-context> <providers> <provider> module:org.code-house.keycloak.login </provider> <!-- .... etc --> You can also try to drop your JAR (if not packaged as module) to ${keycloak.home}/providers directory. Kind regards, Łukasz — Code-House http://code-house.org On 12 Apr 2019, at 10:20, abhishek raghav <abhi.raghav007(a)gmail.com&gt; wrote: Hi - We have implemented a custom account provider which implements AccountProviderFactory and the implementation class extends FreeMarkerAccountProvider. It is packaged and deployed as a provider with a service definition file. This used to be work in keycloak 3.4.3.Final but not after we upgrade to keycloak 4.8.3.Final. We also identified that the provider is not even registering/initialized during boot time of keycloak. Could somebody please tell - whether keycloak has removed support of extending Account provider SPI. Or there is any other way to extend the account provider in keycloak 4.8.3.Final. Any help is greatly appreciated. Thanks -Abhishek _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev