You can override the configured global username by specifying a different username for a group of static subscribers. The username serves as the username for a group of static subscribers that is created and is included in the Access-Request message sent to AAA to authenticate that group.
The username must include at least one of the five possible elements. The value of each element is concatenated in a specific order; the resulting string is the username. If you specify their inclusion, the interface name, logical system name, and routing instance name are derived from the configuration context. The elements are ordered as follows:
user-prefix.interface.logical-system-name.routing-instance-name@domain-name
To configure the username for a group of static subscribers:
- [edit system services static-subscribers group boston authentication
username-include]
- user@host# set user-prefix 2ndFloor
- [edit system services static-subscribers group boston authentication
username-include]
- user@host# set interface
- [edit system services static-subscribers group boston authentication
username-include]
- user@host# set logical-system-name
- [edit system services static-subscribers group boston authentication
username-include]
- user@host# set routing-instance-name
- [edit system services static-subscribers group boston authentication
username-include]
- user@host# set domain-name building5.example.com
Configured in the default logical system and master routing instance for interface ge-0/1/2.50, this sample configuration generates the following username:
2ndfloor.ge-0-1-2-50.default.master.building5.example.com