Auto Scope Mapping

When shared profiles are created in the library and scope mapped to a particular scope in the hierarchy, the referred profiles should be automatically present in the scope. The referred profiles can exist as committed objects or as inherited objects. Essentially, the referred objects must already be scope mapped. For certain profiles such as WLAN ssid profile, the number of referred profiles (direct references as well as nested references) can be large. In such cases, it is cumbersome to map all the referred profiles prior to mapping the WLAN profile itself. Auto scope mapping solves this problem by automatically scope mapping all the necessary referred profiles.

In the above example, some referred profiles are already available at Site 1: prim-srv1 (at Org), auth-grp1 (Site Col), back-srv1 (Current). The remaining referred profiles such as "role-guest", "aaa-cap-prof", "guest-vlan" are not currently scope-mapped to Site 1 or its parents. With auto scope-mapping, you can scope-map "role-guest", "aaa-cap-prof", "guest-vlan" into the site scope. The referred profiles naturally are shared profiles and exists in the library.

When a scope-mapped shared profile is edited (ssid profile in this case), the system automatically takes care of mapping any new references, and un-mapping removed references. For example, if pre-auth-role is changed from "role-guest" to "role-guest1", the system automatically un-maps role-guest and map role-guest1. Similarly, while unmapping an object, the system automatically detects and unmaps the references that were auto-mapped originally.