<?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 can I protect the FusionAuth admin screens from unauthorized access?]]></title><description><![CDATA[<p dir="auto">I'd like to prevent unauthorized users from ever seeing the FusionAuth admin screens. How can I do so?</p>
]]></description><link>https://fusionauth.io/community/forum/topic/148/how-can-i-protect-the-fusionauth-admin-screens-from-unauthorized-access</link><generator>RSS for Node</generator><lastBuildDate>Fri, 10 Apr 2026 15:23:52 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/148.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 08 Jun 2020 21:04:51 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to How can I protect the FusionAuth admin screens from unauthorized access? on Mon, 08 Jun 2020 21:07:13 GMT]]></title><description><![CDATA[<p dir="auto">The way most of our clients handle this is by using proxy redirect rules. For example, if your service is available at <a href="https://auth.example.com" rel="nofollow ugc">https://auth.example.com</a> then you would redirect <a href="https://auth.example.com/" rel="nofollow ugc">https://auth.example.com/</a> to <a href="https://example.com" rel="nofollow ugc">https://example.com</a> to push the user back into the "user" space of your site. This would mean that if you have a FusionAuth admin, they would need to directly access the UI by navigating to <a href="https://auth.example.com/admin/" rel="nofollow ugc">https://auth.example.com/admin/</a>.</p>
<p dir="auto">If you're already using a load balancer or a similar technology that provides routing rules, these are easy to configure.</p>
<p dir="auto">You can also use managed IP locking (limiting access to a certain set of IP addresses), or some other type of HTTP header on the request to limit access to the FusionAuth admin UI to authorized users and treat all other traffic to anything under /admin for end users as an invalid request. These types of solutions are best handled at the network layer or with a proxy.</p>
]]></description><link>https://fusionauth.io/community/forum/post/354</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/354</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Mon, 08 Jun 2020 21:07:13 GMT</pubDate></item></channel></rss>