On May 2, 2014 6:38 PM, "Amogh Vasekar" <[email protected]> wrote: > > Hi, > > On 5/2/14 4:23 PM, "David Bierce" <[email protected]> wrote: > > >In the database you need to increment because things are stored with an ID > >column as the table key, but since cloudmonkey uses the API ID specifies > >the certificate type, not a unique id for the certificate. id=1 for root, > >id=2 for intermediate, id=3 for site certificate. > > For this particular API, the field 'id' passed is stored under a different > column called "seq" in the database - it is used to identify the position > of a particular certificate in the whole chain. > As long as all the ids (i.e 'seq') in the chain are in increasing value > from root to server certificate, it should work. Same value for id may > confuse the SSVM depending on which version you are on.
That is correct. What is different in the way that SSVM uses the key store that would cause it to not function correctly? SSVM works fine on 4.2.1 what versions would not work with multiple intermediate certs. > > HTH > Amogh > > >
