Skip to main content
  • EN

Hi,

We are experiencing an anomalous case on machines where we have installed the NS Client in peruser config mode. We have noticed that when a user with higher client config privileges (disable client, etc.) logs in and subsequently another user connects to the same machine, the second user inherits the client configuration privileges of the user with higher privileges. Only by restarting the service is the client configuration correctly re-established for the user. We noticed this because user 2 now has permissions to disable the client. We have tested it in v123.

 

Estamos experimentando un caso anómalo en máquinas donde tenemos instalado el NS Client con el modo peruser config. Nos hemos dado cuenta que cuando un usuario con mayores privilegios de configuración del cliente (deshabilitar cliente, etc.) inicia sesión y posteriormente otro usuario se conecta a la misma máquina, el segundo usuario hereda los privilegios de configuración del cliente del usuario con mayores privilegios. Solo al reiniciar el servicio se restablece correctamente la configuración del cliente para el usuario. Nos dimos cuenta de esto porque el usuario 2 ahora tiene permisos para deshabilitar el cliente. Lo hemos probado en la versión v123.

 

¿ Os ha ocurrido algo similar? Es un bug?

It is a known, but not officially documented limitation of the Netskope Client in multi-user environments:

 

Thank you Noskope, 

Problem Statement:

Does Netskope allow adjusting the way it handles DNS caching to prevent obsolete IPs from affecting the service?

 

Answer:

Unfortunately there is not settings related to DNS caching, in reality this is not a caching but a mapping done by the ST Agent Driver

I’ve been told by our TAM that in a future release it will be possible to assign client/steering configs by device classification, which will be helpful to deal with this limitation. Though they didn’t give me a timeline.

Reply


Terms & ConditionsCookie settings