Project

General

Profile

Bug #5663

allow webcertificates details to be specified via files

Added by Constantin Asofiei over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:

Related issues

Related to Runtime Infrastructure - Feature #3240: setup and use of real SSL certificates (NOT self-signed) Closed

History

#1 Updated by Constantin Asofiei over 2 years ago

  • Related to Feature #3240: setup and use of real SSL certificates (NOT self-signed) added

#3 Updated by Constantin Asofiei over 2 years ago

Currently the structure of the webCertificates is this:

         <node class="container" name="webCertificates">
           <node class="container" name="standard">
             <node class="string" name="alias">
               <node-attribute name="value" value="[web-alias]"/>
             </node>
             <node class="bytes" name="certificate">
               <node-attribute name="value" value="[the generated certificate for this alias]"/>
             </node>
             <node class="container" name="chain">
               <node class="bytes" name="[the alias for the root certificate]">
                 <node-attribute name="value" value="[the root CA certificate used to sign the certificate]"/>
               </node>
             </node>
             <node class="container" name="key">
               <node class="bytes" name="key-entry">
                 <node-attribute name="value" value="[the private key for the certificate encrypted with key-password]"/>
               </node>
               <node class="bytes" name="key-password">
                 <node-attribute name="value" value="[the encryption password for the 'key-entry' above]"/>
               </node>
             </node>
           </node>
        </node>

We should allow files to specify the certificate, the root CA chain and the private key.

Also available in: Atom PDF