Configuring Subscriber Filtering for General Authentication Service Trace Operations
Starting in Junos OS Release 14.1, you can apply filters to the general authentication service to limit tracing to particular subscribers or domains. Subscriber filtering simplifies troubleshooting in a scaled environment by enabling you to focus on a reduced set of trace results.
For subscriber usernames that have the expected form of user@domain, you can filter on the user, the domain, or both. You can use an asterisk (*) as a wildcard to substitute for characters at the beginning or end of either term to match a greater number of subscribers.
You cannot filter results using a wildcard in the middle of the user or domain terms. For example, the following uses of the wildcard are not supported: email@example.com, tom125@ex*.com.
When you enable filtering by username, traces that have insufficient information to determine the username are automatically excluded.
To configure subscriber filtering:
Specify the filter.user@host# set filter user user@domain
Consider the following examples of using the wildcard for filtering:
Filter results for the specific subscriber with the username, firstname.lastname@example.org@host# set filter user email@example.com
Filter results for all subscribers whose username begins with tom.user@host# set filter user tom*
Filter results for all subscribers whose username ends with tom.user@host# set filter user *tom
Filter results for subscribers with the username tom at all domains beginning with ex.user@host# set filter user tom@ex*
Filter results for all subscribers at all domains that end with ample.com.user@host# set filter user *ample.com
Filter results for all subscribers whose username begins with tom at domains that end with example.com.user@host# set filter user tom*@*example.com