Token seed file format

DualShield(V5x) is very different from its predecessor(Deepnet UAP V3x). Even the SafeID token seed file has different formats.

Deepnet UAP (V3x) Format

<tokenList>
<tokenInfo>
<method>PocketID</method>
<device>
<manufacturer>Deepnet Security</manufacturer>
<vendor>Deepnet Security</vendor>
<model>TB</model>
<serial>71358472</serial>
</device>
<token><![CDATA[<data>
<deviceID>71358472</deviceID>
<type>TB</type>
<counter>0</counter>
<digits>6</digits>
<secret enc="HEX">08E49538328BAE830E0DB14A82341100BC23B840</secret>
<description>71358472</description>
</data>
]]></token>
</tokenInfo>
</tokenList>

DualShield (V5x) Format

<?xml version="1.0"?>
<data>
 <header>
  <manufacturerCode>DN</manufacturerCode>
  <productCode>ST</productCode>
  <encode>HEX</encode>
  <encrypt>NONE</encrypt>
 </header>
 <tokens>
  <token>
   <serial>71358472</serial>
   <seed>08E49538328BAE830E0DB14A82341100BC23B840</seed>
  </token>
 </tokens>
</data>

You can ask our sales for new seed file if you migrate from V3x to V5x, alternatively you can edit the existing token seed file directly, based on the above formats.