# Limit access to Node-RED via client certificates

**URL:** <https://discourse.nodered.org/t/limit-access-to-node-red-via-client-certificates/83996>\
**Category:** Share Your Projects\
**Tags:** security\
**Created:** [23 December 2023 22:40 UTC](https://discourse.nodered.org/t/limit-access-to-node-red-via-client-certificates/83996 "2023-12-23T22:40:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [24 December 2023 10:21 UTC](https://discourse.nodered.org/t/limit-access-to-node-red-via-client-certificates/83996/4 "2023-12-24T10:21:15Z")

</div>

> [@BartButenaers](#):
>
> What I liked more in your proposal, is the fact that you only have to make adjustements in your Node-RED server

I think my aim for it, is to allow the inexperienced users to have a barrier without trying to understand the various products / services that are around.

It's been updated and now uses a built in class to help add the IP Address', Ranges & Subnets.

example:

```auto
const allowedIPs = [
  "127.0.0.1", /* Localhost */
  "172.16.0.0/24", /* Private Network */
  "103.22.200.1-103.22.203.254" /* CloudFlare range example */
];

```

Taking out the hosted services from the equation, both the client cert and IP White listing approach are both extremely powerful mechanisms! 🤓

Note: I added the the **security** tag to this post

---

_[View the full topic](https://discourse.nodered.org/t/limit-access-to-node-red-via-client-certificates/83996)._