Can't select users in policy

[cryptochrome]

Hi,

I am playing with my little PA-200 and wanted to try user based policies. I added a couple of users to the local user database and grouped them into user groups. Now when I create a new policy (or modify an existing one), the source-user field stays empty, my users don't show up so I can't add them. Even when I start typing (for autocomplete) I don't get any results.

Captive Portal, auth profile etc. are all configured as per documentation, and the interface is configured for UserID.

What am I missing here?

Thanks

Sascha

[sraghunandan]

Hi Sascha,

Firstly the local db users can be used only after you get the captive portal page (once you get the cp page enter the username that when we get the user to ip mapping ) i.e once the auth is successful that when you can have the policies using the local db users.So i would suggest you to have a sec policy allowing unknown users under the user field select unknown or leave it to any and set the application to web browsing,dns. Then you can have a policy below it with the local user specified and then regulate it accordingly.

Thank you.

Subijith Raghunandan.

[cryptochrome]

Looks like we're getting closer    So why two policies? Can't I put this in one policy? Destination server is HTTP, but operates on port 10001.

Thanks

Sascha

[sraghunandan]

Hello Sascha,

The user is not identified until and unless we have him login to the cp page so in order to get there we need a policy allowing it, and later on once we are identified (ie user to mapping is formed) then the second rules comes in to play.

We always look at the ip of the incoming traffic first and then look to see if there is a mapping for it.

The second policy with the user in can have the dest set to the http server and the port 10001.

Thank you.

Subijith Raghunandan.

[cryptochrome]

Thanks. I am still puzzeled by the first policy you mention. My understanding was that the captive portal is transparent. So if I set up a rule that requires a user to authenticate, shouldn't captive portal page show up transparently and thus only one policy necessary?

Anyways... so the first policy is set to unknown user to get the captive portal page to show up. But what do I allow in the first rule and to which destination? If my actual matching rule is supposed to be the second one, what do I put in the first? Sorry, but this kind of evades my logic :smileygrin:

Cheers

Sascha

[sraghunandan]

Hello Sascha,

The traffic flow is as follows :-

Broswer--type in an url--the traffic hits the pa (at this moment the user is not known to the fw ) it looks at the dest ip and its relevant zone. so first and foremost we need a policy to allow this, once this is allowed the traffic hits the cp policy and the page shows up.

Thank you.

Subijith Raghunandan.