Setting up a filtering service with NXCloud

[SteveHughes]

Hi, I'm trying this out as a possible MSP service we can offer to our client base. I cant see how to use any of the SSO agents in NXcloud - the setup options just dont seem to exist. I may be missing something.

Is anyone sucessfully using NXcloud in a MSP environment? Keen to hear thoughts and tips.

Thanks,
Steve

[support200]

If you're referring to SSO agents with AD integration, they don't work beyond a router. However, AD integration can be partially implemented using NxRelay and NxCloud: https://tutorial.nxfilter.org/d-nxre...le-network.php.

For a few users requiring different policies, you can try NxProxy: https://tutorial.nxfilter.org/d-nxpr...-filtering.php.

[SteveHughes]

Thanks. We have a couple of sites that run AD locally, but more and more we are dealing with fully mobile users defined in Azure AD, and operating from random locations. Would NxProxy be the tool for this?

[support200]

You can associate a user to NxProxy. Wherever it goes it filters user DNS requests as long as it can connect NxCloud. It's basically a remote filtering agent.

[SteveHughes]

I tried that on my home PC and it works fine thanks. But I had to create the user manually in nxfilter in order to get the token. We have an RMM whcih will allow us to mass-deploy NxProxy to a fleet of laptops, but is there a way to do this without having to manually generate a separate token for each laptop?

[support200]

You can use the same token for multiple users. In your log view,, it will appear as 'tokenUserName_windowLoginName'. When you have a matching username with windowLoginName in your user list then it becomes the matching user.

For example, when you have 'nxproxy' user on NxCloud and when the logged-in user name on the system your NxProxy running on is 'johndoe', it becomes 'nxproxy_johndoe'. But if you have 'johndoe' user on NxCloud then it becomes 'johndoe'.

In NxCloud case, I guess it's better not to have a matching user especially when you have many users. You can treat the Token User as a group. What you want is to differentiate who's who and assign a group policy to them.

[support200]

Somehow the explanation about this is missing in our tutorial and we are writing it.