You configure additional entries in the subscriber classification script to support services for IDP integration.
To add entries to a subscriber classification script to support IDP integration:
To view the sample subscriber classifications referenced in this section, see l=IDP, l=SAE, ou=staticConfiguration, ou=Configuration, o=Management, o=umc in the sample data.
For JUNOSe routers the subscriber classification script must assign a subscriber profile to the router interface. For example:
- [ou=routers,retailername=SP-IDP,o=Users,o=UMC??sub?(routerName=<-virtualRouterName->)]
- # host subscriber for JUNOSe routers
- interfaceName=="Router"
For JUNOSe routers the subscriber classification script must also assign a shared subscriber profile and a login name to a subscriber session when a core interface service is activated. The following example assigns a login name and IP address for the subscriber session to an interface that has core specified as the ifAlias (as configured on the JUNOSe router).
- [routerName=idp,ou=interfaces,retailername=SP-IDP,o=Users,o=UMC
?loginName=idp@idp]
- # core facing interfaces on JUNOSe routers in JUNOSe POPs
- ifAlias=="core"
The login name specified in this classification must be the same as the value set in the subscriber reference expression for the core interface fragment service in the aggregate service. The interface alias must be the same as the one specified in the interface classification script.
For JUNOS routing platforms, the subscriber classification script must assign subscriber profiles for the forwarding interface. For example:
- [ou=routers,retailername=SP-IDP,o=Users,o=UMC??sub?(routerName=
<-virtualRouterName->)]
- # host subscriber for JUNOS routers
- interfaceName=="FORWARDING_INTERFACE"
For general information about classifying subscribers, see Overview of Classification Scripts .