Changes between Version 1 and Version 2 of Ticket #1383, comment 3


Ignore:
Timestamp:
02/08/21 15:26:59 (6 months ago)
Author:
Selva Nair
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1383, comment 3

    v1 v2  
    66I can only say you have to somehow ensure the group membership is recognized on the machine. Generally whoami /groups should show it.
    77
    8 That is, if have "OpenVPN Administrators" group on the local machine, and the relevant AD group containing the user has been added to it, "whoami /groups" will list "OpenVPN Administrators" as one of the groups the user belongs to. If it does not, the GUI also may not be able to recognise that the user is in that group. Maybe something is wrong with the Azure setup?
     8That is, if you have "OpenVPN Administrators" group on the local machine, and the relevant AD group containing the user has been added to it, "whoami /groups" will list "OpenVPN Administrators" as one of the groups the user belongs to. If it does not, the GUI also may not be able to recognise that the user is in that group. Maybe something is wrong with the Azure setup?
    99
    1010That said, I do not know how Azure dynamic groups work. We only look for the group SID in the process token.