06-04-2020 01:22 PM
I have a very simple problem in that I need to bypass a set of endpoints from a policy. I am in conditions studio and am trying to use the "in". For example, as a test I am trying to use
Radius User-Name In {username list}
I've tried space delimited, then comma, coma space, pipe and haven't had success yet. Anyone have an "IN" example for me to get a clue? I'm sure once I see it, I'll feel foolish, but I am what I am. I have a lot of policies, but have never used IN before and just keep missing it. Of course, it works with one item, but after that I am failing.
I'll keep on looking for documentation or an example and keeping trying to guess at the syntax.
Thank you.
Solved! Go to Solution.
06-04-2020 02:24 PM - edited 06-04-2020 02:26 PM
I never did figure it out. I tried 8 various combinations of delimited lists. I finally bailed and with went with this MATCHES using regex string. I need to do some more testing, but it seems to work so far.
(?i)user1|user2|user3
06-04-2020 03:33 PM
Yes, you need to use MATCHES with regex if comparing against list of usernames defined in the condition. IN is used to find out if the user is in the existing AD/LDAP group or internal user/endpoint group.
06-04-2020 02:24 PM - edited 06-04-2020 02:26 PM
I never did figure it out. I tried 8 various combinations of delimited lists. I finally bailed and with went with this MATCHES using regex string. I need to do some more testing, but it seems to work so far.
(?i)user1|user2|user3
06-04-2020 03:33 PM
Yes, you need to use MATCHES with regex if comparing against list of usernames defined in the condition. IN is used to find out if the user is in the existing AD/LDAP group or internal user/endpoint group.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide