Hi, we run a multi portal instance of DNN and would like to allow access to any of the portal login pages to 1 or 2 specified IP Address only, therefore restricting access to our own network users only.. I see lots of example of limiting whole websites to IP, but I want the public to be able to access the sites as normal just not the login pages.
I believe this can be done via the web config so just looking for best examples how we might achieve this and perhaps re-direct blacklisted users somewhere else (maybe a message page)?
Posted By Stuart on 01 May 2020 05:15 AM Hi, we run a multi portal instance of DNN and would like to allow access to any of the portal login pages to 1 or 2 specified IP Address only, therefore restricting access to our own network users only.. I see lots of example of limiting whole websites to IP, but I want the public to be able to access the sites as normal just not the login pages. I believe this can be done via the web config so just looking for best examples how we might achieve this and perhaps re-direct blacklisted users somewhere else (maybe a message page)?
AFAIK DNN 9 has that option under security > login settings > login ip filters
Hmm, I though it was for anyone. If you need more specific filtering a custom authentication provider (requires .net development) is the only reliable option I know of.
IIS Redirect module is good solution if it's available/installed on your server. Probably way easier than developing a custom authentication provider. Another solution is to use Cloudflare. I made the move to Cloudflare a year ago and it's working really well. I removed all the IIS Redirect rules and use Cloudflare firewall rules instead.
That is a very good idea
These Forums are for the discussion of the open source CMS DNN platform and ecosystem.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.