<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[How to install a custom password hashing plugin and ensure correct package naming?]]></title><description><![CDATA[<p dir="auto">I've developed a custom password hashing plugin for FusionAuth that implements several legacy password schemes. However, I've encountered an issue with plugin installation:</p>
<p dir="auto"><strong>Initial Problem:</strong><br />
The plugin JAR (version 1.0.0) was not being loaded by FusionAuth. The Guice module was in the package <code>au.com.company.fusionauth.product</code> but FusionAuth didn't install it and provided no error message.</p>
<p dir="auto"><strong>Plugin Details:</strong></p>
<ul>
<li>Custom password encryptor plugin</li>
<li>Registers three custom password schemes</li>
<li>Built against fusionauth-plugin-api 1.16.0</li>
<li>Compiled for Java 17</li>
<li>Running on FusionAuth 1.70.0 (which uses Java 25)</li>
</ul>
<p dir="auto"><strong>Questions:</strong></p>
<ol>
<li>What are the package naming requirements for FusionAuth plugins?</li>
<li>How can I confirm that a plugin has loaded successfully?</li>
<li>What's the proper procedure for updating/replacing a plugin version?</li>
<li>Will plugins persist through FusionAuth version upgrades?</li>
</ol>
]]></description><link>https://fusionauth.io/community/forum/topic/3410/how-to-install-a-custom-password-hashing-plugin-and-ensure-correct-package-naming</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 09:45:26 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/3410.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 18 Nov 2026 21:57:34 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to How to install a custom password hashing plugin and ensure correct package naming? on Wed, 18 Nov 2026 21:57:45 GMT]]></title><description><![CDATA[<h2>Package Naming Requirement</h2>
<p dir="auto">FusionAuth has a specific package naming requirement for plugins: <strong>the <code>@PluginModule</code> class must be in a package that has a parent package named "plugin" or "plugins"</strong>.</p>
<p dir="auto">For example:</p>
<ul>
<li><img src="https://fusionauth.io/community/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/2705.png?v=rcgg4tg866g" class="not-responsive emoji emoji-android emoji--white_check_mark" style="height:23px;width:auto;vertical-align:middle" title=":white_check_mark:" alt="✅" /> <code>au.com.company.fusionauth.plugins.product.MyPluginModule</code></li>
<li><img src="https://fusionauth.io/community/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/2705.png?v=rcgg4tg866g" class="not-responsive emoji emoji-android emoji--white_check_mark" style="height:23px;width:auto;vertical-align:middle" title=":white_check_mark:" alt="✅" /> <code>au.com.company.fusionauth.plugin.product.MyPluginModule</code></li>
<li><img src="https://fusionauth.io/community/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/274c.png?v=rcgg4tg866g" class="not-responsive emoji emoji-android emoji--x" style="height:23px;width:auto;vertical-align:middle" title=":x:" alt="❌" /> <code>au.com.company.fusionauth.product.MyPluginModule</code> (will be skipped silently)</li>
</ul>
<p dir="auto">If the package structure doesn't follow this convention, FusionAuth will skip the plugin JAR without displaying an error.</p>
<h2>Installation Process</h2>
<ol>
<li>
<p dir="auto"><strong>Create the plugins directory</strong> in your FusionAuth installation (peer to the <code>bin</code> and <code>config</code> directories):</p>
<ul>
<li><strong>Linux/macOS:</strong> <code>/usr/local/fusionauth/plugins</code></li>
<li><strong>Windows:</strong> <code>\fusionauth\plugins</code></li>
</ul>
</li>
<li>
<p dir="auto"><strong>Place the plugin JAR file</strong> in the FusionAuth plugins directory</p>
</li>
<li>
<p dir="auto"><strong>Restart FusionAuth</strong> (this will cause 1-2 minutes of downtime)</p>
</li>
<li>
<p dir="auto"><strong>Check the startup logs</strong> for confirmation messages:</p>
<pre><code>INFO io.fusionauth.api.plugin.guice.PluginModule - Installing plugin [au.com.company.fusionauth.plugins.product.MyPluginModule]
INFO io.fusionauth.api.plugin.guice.PluginModule - Plugin successfully installed
</code></pre>
</li>
</ol>
<h2>Confirming Plugin Installation</h2>
<p dir="auto">You can verify that your custom password hashing plugin loaded successfully through the Admin UI:</p>
<ol>
<li>Navigate to <strong>Tenants → [Your Tenant] → Password</strong></li>
<li>Scroll to <strong>Cryptographic hash settings</strong></li>
<li>Look for your custom scheme(s) in the <strong>Scheme</strong> dropdown field</li>
</ol>
<p dir="auto">If your custom schemes appear in this dropdown, the plugin has been successfully installed.</p>
<h2>Updating a Plugin</h2>
<p dir="auto">When replacing a plugin version:</p>
<ol>
<li><strong>Remove the old JAR file</strong> from the plugins directory (don't leave multiple versions installed if they register the same scheme names)</li>
<li>Install the new JAR file</li>
<li>Restart FusionAuth</li>
<li>Verify the new version loaded via the startup logs</li>
</ol>
<p dir="auto"><strong>Note:</strong> You should never delete an installed password hashing plugin unless you are certain that no users are using the hash provided by that plugin. If any users still have that <code>encryptionScheme</code> associated with their account, FusionAuth will not be able to validate their password.</p>
<h2>Plugin Persistence Through Upgrades</h2>
<p dir="auto">Plugins should generally persist through FusionAuth version upgrades. However, since FusionAuth bundles its own Java runtime and that runtime version can change between major FusionAuth versions, you may need to rebuild your plugin for compatibility with newer Java versions. It's advisable to test plugin compatibility when planning FusionAuth upgrades.</p>
<h2>Java Compatibility Note</h2>
<p dir="auto">FusionAuth ships with its own bundled Java runtime. The version depends on your FusionAuth version. For example, FusionAuth 1.70.0 uses Java 25. If your plugin is compiled for Java 17, it should be compatible with Java 25 (forward compatibility), but always test in your environment to confirm.</p>
<hr />
<h2>Related Documentation</h2>
<ul>
<li><a href="https://fusionauth.io/docs/migrate/password-hashes/writing-a-plugin#install-the-plugin" rel="nofollow ugc">Writing a Plugin - Install the Plugin</a> - Detailed installation instructions and directory structure</li>
<li><a href="https://fusionauth.io/docs/migrate/password-hashes/writing-a-plugin#create-the-guice-binding" rel="nofollow ugc">Writing a Plugin - Create the Guice Binding</a> - Package naming requirements for plugins</li>
<li><a href="https://fusionauth.io/docs/migrate/password-hashes/custom-password-hashing" rel="nofollow ugc">Custom Password Hashing</a> - Overview of custom password hashing plugins</li>
<li><a href="https://fusionauth.io/docs/deploy/troubleshoot/troubleshooting#troubleshooting-custom-password-hashing-plugins" rel="nofollow ugc">Troubleshooting Custom Password Hashing Plugins</a> - Common issues and verification steps</li>
<li><a href="https://fusionauth.io/docs/migrate/password-hashes/custom-password-hashing#deleting-plugins" rel="nofollow ugc">Custom Password Hashing - Deleting Plugins</a> - Important considerations when removing plugins</li>
<li><a href="https://fusionauth.io/docs/migrate/password-hashes/" rel="nofollow ugc">Password Hashing Plugins Overview</a> - General information about FusionAuth's plugin mechanism</li>
<li><a href="https://github.com/FusionAuth/fusionauth-example-password-encryptor" rel="nofollow ugc">Example Password Encryptor Plugin</a> - Sample plugin project on GitHub</li>
</ul>
]]></description><link>https://fusionauth.io/community/forum/post/9161</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/9161</guid><dc:creator><![CDATA[FASupportBot]]></dc:creator><pubDate>Wed, 18 Nov 2026 21:57:45 GMT</pubDate></item></channel></rss>