User Matcher: Difference between revisions
From Edge Threat Management Wiki - Arista
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
|+ | |+ | ||
! Name !! Example !! Description | ! Name !! Example !! Description | ||
|- | |- | ||
| Any Authenticated User | | Any Authenticated User | ||
| [authenticated] | | [authenticated] | ||
| matches all identified or authenticated users | | matches all identified or authenticated users (excluding null) | ||
|- | |- | ||
| Unauthenticated User | | Unauthenticated User | ||
| [unauthenticated] | | [unauthenticated] | ||
| matches all unidentified or unauthenticated users | | matches all unidentified or unauthenticated users (including null) | ||
|- | |- | ||
| Username | | Username | ||
Latest revision as of 03:08, 8 March 2017
User Matcher syntax is a that describes an user or set of users. This can be used, for example, in Policy Manager or Bandwidth Control rules to match against certain traffic.
User Matcher can be any of the following:
| Name | Example | Description |
|---|---|---|
| Any Authenticated User | [authenticated] | matches all identified or authenticated users (excluding null) |
| Unauthenticated User | [unauthenticated] | matches all unidentified or unauthenticated users (including null) |
| Username | myuser | matches the "myuser" user |
| Glob Matcher | m*r | matches the "myuser" user |
| List of User Matchers | myuser1,myuser2 | matches "myuser1" and "myuser2" |
