Skip to main content

I need to apply different Netskope client/steering configurations to local users who are not managed by my external IDP (Entra / OneLogin etc...).

Currently the only way to assign client/steering configs is via groups but as this is a local user, the default is then used, which is not a viable option to modify. 

To address this, could Netskope please consider implementing one of the following options:

  1. Direct User Assignment: Allow administrators to assign client and steering configurations directly to individual users, even if they are local users.

  2. Local Groups in Netskope: Enable the creation of local user groups within Netskope, independent of the external IDP, to allow for flexible configuration assignments.

This question comes up a lot here. It doesn’t seem like Netskope is going to do this anytime soon, so here are some suggestions that will work:

 

  • You can manage “local” user/groups and their memberships via the SCIM API. It’s not particularly convenient, but it works.
  • If you are not using your IDP due to licensing cost, you can deploy an open source IDP called Authentik that supports SCIM for these users. It’s easier than doing it manually via API once you have it going.

 

 


Thank you for the response!

This is a shame that something cannot be done natively within the platform but will take a look at both solutions you have suggested. 

 

Thanks


Reply