About novidys

I got a response from support. The issue is known as a bug and may be fix in 3.1.7. To get all agent sending information, we can execute the command: debug software restart device-server Bye, ... View more

Thanks, But, all of the agents are connected (and status ok) with the command " show user pan-agent statistics ". I also try "debug device-server reset pan-agent all" but it doesn't change anything. When I execute the command show user ip-user-mapping, a lot of IP address have the second and third column as "Unknown". And only IP of the network of the primary agent have these columns with a value (AD and user). When we look on one agent in a DC, we have no errors in the "Agent status" field, and we success to get all the mapping IP/user with a "get all" button in "IP to Username information" section. ... View more

Ok mike. So if i reformulate your answer. If in my allow list, I have the following group: NOVIDYS\tech. And in the AD, Bob belongs to NOVIDYS. When Bob want to connect to the SSL VPN he only submit Bob. Then the PAN append NOVIDYS to Bob ("NOVIDYS\Bob") and check if he belongs to NOVIDYS\tech (wich is in the allow list) regarding the information the Pan-agent gave to the PAN. Best regards, ... View more

Hi, My question was not concerning the stage of the authentification with the RADIUS but the stage after (authorisation). Let's take the precedent exemple to explain our interrogation. From our understanding of the PAN when a user wants to connect to the SSL VPN there are several steps: The user connect to the url of the VPN SSL Submit his login and password The radius server is first solicited for the authentication stage. The login and password are submitted from the PAN to the Radius server. The Radius then check if the password match for the login. Then is everything is OK the client is authenticated. After that. There is the stage of the authorisation. The allow list which is associated to the VPN SSL (the user is connected on) is checked. The PAN verify if the login belongs to a group wich is specified in the allow list. This permit after to mount the SSL VPN for that user. Regarding that. The authentication profil (AdminAuthProfil) for the SSL VPN is configured like this this: Authentication method: RADIUS Allow list: AD Groups taken from the User-ID agent. In the allow list we have DOMAIN\admin. The question is (still regarding our exemple) : When user connects to the SSL VPN the login that was submitted was AdminLogin and not DOMAIN\AdminLogin. So when it's the turn of the authorisation stage. When AdminLogin connect to the SSL VPN, The PAN will check for the presence of AdminLogin in the group DOMAIN\admin regarding the "allow list". Or it will fail because the login is not presented like the AD form (DOMAIN\AdminLogin). Thank you in advance. Best regards, ... View more