Provisioning Examples
Profile Management
Provisioning Guide for Cisco SPA100 and SPA200 Series Analog Telephone Adapters
62
4
Upon resync, the new file is downloaded by the ATA and used to update its
parameters.
Profile Encryption by using OpenSSL
A compressed or uncompressed profile can be encrypted (however, a file must
be compressed before it is encrypted). This is useful when the confidentiality of
the profile information is of particular concern, such as when using TFTP or HTTP
for communication between the ATA and the provisioning server.
Exercise
STEP 1
Install OpenSSL on a local PC. This might require that the OpenSSL application be
recompiled to enable AES.
STEP 2
Using the
basic.txt
configuration file (described in the
TFTP Resync
exercise),
generate an encrypted file with the following command:
>openssl enc –aes-256-cbc –k MyOwnSecret –in basic.txt –out basic.cfg
The compressed basic.txt.gz file created in
Open Profile gzip Compression
also
can be used, because the XML profile can be both compressed and encrypted.
STEP 3
Store the encrypted basic.cfg file in the TFTP server virtual root directory.
STEP 4
Modify the Profile_Rule on the test device to resync to the encrypted file in place
of the original XML file. The encryption key is made known to the ATA with the
following URL option:
[--key MyOwnSecret ] tftp://192.168.1.200/basic.cfg
STEP 5
Click
Submit All Changes
.
STEP 6
Observe the syslog trace from the ATA.
On resync, the new file is downloaded by the ATA and is used to update its
parameters.
