Cisco SPA Fusion Template Password Bug

Status
Not open for further replies.

bcmike

Active Member
Jun 7, 2018
337
58
28
53
Hi,

I have discovered an incompatibility in the way that Fusion generates random passwords and the way that the Cisco SPA templates generate XML. If Fusion generates a password with an ampersand in it the template will generate an XML file with the ampersand between the tags. In XML an ampersand is an illegal character unless properly escaped, thus the phone will not properly process the file generated as it'll break at the password tag. The result is the phone will not properly provision.

Example:

XML:
<Password_1_ group="Ext_1/Subscriber_Information">%^&xMQmYSu</Password_1_>

Will not be processed and will fail to provision properly.

This may effect other templates as well, although I have not tested.
 

bcmike

Active Member
Jun 7, 2018
337
58
28
53
Update: This does not seem to effect any of the other XML based templates. There must be something special about the way the Cisco XML is parsed.
 
Status
Not open for further replies.