Cisco Cisco Identity Services Engine 1.3 릴리즈 노트

Ensure that you have the Active Directory credentials if you are using Active Directory as your external 
identity source. After an upgrade, you might lose Active Directory connections. If this happens, you 
must rejoin Cisco ISE with Active Directory. After rejoining, perform the external identity source call 
flows to ensure the connection.

The upgrade process does not migrate all sponsor groups. Sponsor groups that are not used in the 
creation of guests roles are not migrated. As a result of this change, some sponsors (internal database or 
Active Directory users) may not be able to log in after upgrade to Release 1.3.

Check the sponsor group mapping for sponsors who are not able to log in to the sponsor portal, and map 
them to the appropriate sponsor group.

After upgrading to Cisco ISE 1.3, the new guest types that are created do not match the upgraded 
authorization policies. You need to make sure that the authorization policies are updated with the new 
guest types.

The order in which Network Interface Cards (NICs) are connected to Cisco UCS SNS 3415 and Cisco 
UCS SNS 3495, and IBM Cisco ISE 3315 appliances may affect the upgrade to ISE 1.3. You should 
ensure that a pre-upgrade check is performed, followed by sequencing of the NICs. Perform a 
pre-upgrade check of NICs for UCS and IBM Appliances to ensure that Ports eth0 and eth1 should be 
used for Intel NICs on UCS appliances and, ports eth2 and eth3 should be used for Broadcom NICs on 
IBM appliances. Refer to the Sequence Network Interface Cards (NICs) for UCS and IBM Appliances 
section in the 

Cisco ISE, Release 1.3 provides a new streamlined guest and employee on-boarding experience as well 
as a new portal customization experience with a host of new features from multi-language support to 
WYSIWYG customization. When you upgrade to Release 1.3, all custom portals are migrated to the new 
ISE 1.3 experience. Here are a few considerations that you must be aware of: 

The basic look and feel customizations that were done using CSS & HTML in previous releases of 
ISE are migrated by the upgrade process to 1.3 in to the new Guest and Personal Devices flows. 

Customizations that use custom JavaScript to alter the Guest flow might not migrate properly. You 
can recreate these flows from the ISE 1.3 Admin portal. You do not require any coding skills to 
perform these customizations in Release 1.3. 

You cannot edit any of the custom portals that are migrated to Release 1.3. If you want to make 
changes to the look and feel, you must create a new portal. You do not require any coding skills to 
create a new custom portal in Release 1.3. 

ISE 1.2 customers were capable of making a wide variety of portal customizations. Some of those 
customizations might not migrate to ISE 1.3 predictably. We recommend you review your newly 
migrated portals in a lab setting before using them in a production environment.