Overlapping GlobalProtect Portal agent config AD groups
Does anyone know how Palo treats overlapping Active directory groups for portal agent configs? Is the list read top down for handing out configurations to the agent if a user exists in multiple groups identified by the portal?




