<?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 restrict FusionAuth admin panel access to specific IP addresses?]]></title><description><![CDATA[<p dir="auto">We want to restrict access to the FusionAuth admin panel so that only our internal network can reach it, while keeping the rest of the service (user login, APIs, etc.) accessible to all users from anywhere.</p>
<p dir="auto">Specifically:</p>
<ul>
<li>Admin panel should only be accessible from our corporate network IP addresses (e.g., VPN and secure access gateway IPs)</li>
<li>All other FusionAuth functionality (OAuth flows, user authentication, APIs) should remain publicly accessible</li>
<li>We're using FusionAuth Cloud</li>
</ul>
<p dir="auto">Is there a way to implement IP-based access control for just the admin interface? Also, what's the recommended fallback approach if we accidentally lock ourselves out?</p>
]]></description><link>https://fusionauth.io/community/forum/topic/3285/how-to-restrict-fusionauth-admin-panel-access-to-specific-ip-addresses</link><generator>RSS for Node</generator><lastBuildDate>Wed, 04 Nov 2026 03:20:01 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/3285.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 28 Oct 2026 14:56:39 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to How to restrict FusionAuth admin panel access to specific IP addresses? on Tue, 03 Nov 2026 14:57:37 GMT]]></title><description><![CDATA[<h2>Recommended Approaches for FusionAuth Cloud</h2>
<p dir="auto">Since you're using FusionAuth Cloud, here are your options for restricting admin panel access:</p>
<h3>Use IP ACLs</h3>
<p dir="auto">You can use the IP ACLs and assign them to the <code>FusionAuth</code> application, which represents the FusionAuth admin UI.</p>
<p dir="auto">These are an enterprise only feature, so if you are not on that plan, you can't use IP ACLs.</p>
<h3>Additional Security Layers</h3>
<p dir="auto">While these don't replace IP restrictions, they add defense in depth:</p>
<ul>
<li><strong>Tenant Separation</strong>: Move all non-admin users to a separate tenant, keeping the default tenant for administrators only</li>
<li><strong>Strong MFA</strong>: Require multi-factor authentication for all admin users</li>
<li><strong>API Key Security</strong>: If you use IP ACLs with API keys (see below), you can restrict which IPs can use specific API keys</li>
</ul>
<h2>What IP ACLs ARE Good For</h2>
<p dir="auto">While IP ACLs don't protect the admin UI directly, they're still valuable for:</p>
<ol>
<li><strong>Restricting application access</strong> - Apply an IP ACL to specific applications to limit which IPs can authenticate to those apps</li>
<li><strong>Restricting tenant access</strong> - Apply an IP ACL to a tenant to limit logins across all applications in that tenant</li>
<li><strong>Restricting API key usage</strong> - Apply an IP ACL to API keys to limit which IPs can use them</li>
</ol>
<p dir="auto">To configure an IP ACL:</p>
<ol>
<li>Navigate to <strong>Settings &gt; IP Access Control</strong></li>
<li>Click the <strong>+</strong> icon to create a new ACL</li>
<li>Add IP ranges and specify whether to allow or block them</li>
<li>Set a default action (allow or block) for IPs that don't match any defined range</li>
<li>Assign the ACL to an Application, Tenant, or API Key</li>
</ol>
<h2>Emergency Access / Lockout Prevention</h2>
<p dir="auto"><strong>Before implementing any IP restrictions</strong> (whether via proxy or IP ACLs):</p>
<ol>
<li><strong>Create a backup API key</strong> with full admin privileges that you store securely</li>
<li><strong>Test your configuration</strong> from an allowed IP address first</li>
<li><strong>Document your IP ranges</strong> and keep them updated</li>
<li><strong>Have a rollback plan</strong> - If using a proxy, ensure you can quickly remove or modify the IP restrictions</li>
</ol>
<p dir="auto">If you do get locked out:</p>
<ul>
<li>With IP ACLs on API keys/tenants: Use an unrestricted API key to call the FusionAuth API to modify or remove the ACL</li>
<li>Last resort: Contact support (Cloud)</li>
</ul>
<h2>Related Documentation</h2>
<ul>
<li><a href="https://fusionauth.io/docs/operate/secure/advanced-threat-detection#ip-access-control-lists" rel="nofollow ugc">Advanced Threat Detection - IP Access Control Lists</a></li>
<li><a href="https://fusionauth.io/docs/apis/ip-acl/" rel="nofollow ugc">IP Access Control List API</a></li>
<li><a href="https://fusionauth.io/docs/operate/secure/networking" rel="nofollow ugc">Networking Configuration (Trusted Proxies)</a></li>
<li><a href="https://fusionauth.io/docs/get-started/run-in-the-cloud/cloud" rel="nofollow ugc">FusionAuth Cloud Deployment</a></li>
<li><a href="https://fusionauth.io/community/forum/topic/2974/how-to-restrict-fusionauth-admin-panel-access-by-ip-address">Community Forum: Restricting Admin Panel Access</a></li>
</ul>
]]></description><link>https://fusionauth.io/community/forum/post/8908</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/8908</guid><dc:creator><![CDATA[FASupportBot]]></dc:creator><pubDate>Tue, 03 Nov 2026 14:57:37 GMT</pubDate></item></channel></rss>