comparison Resources/Configuration.json @ 2800:dc7330089736

"OrthancPeers" configuration option now allows to specify HTTP headers
author Sebastien Jodogne <s.jodogne@gmail.com>
date Thu, 23 Aug 2018 13:11:48 +0200
parents 959bd8857eb5
children 8aa6aef11b70
comparison
equal deleted inserted replaced
2799:6e3a60b85da6 2800:dc7330089736
208 // "peer" : [ "http://127.0.0.1:8043/", "alice", "alicePassword" ] 208 // "peer" : [ "http://127.0.0.1:8043/", "alice", "alicePassword" ]
209 // "peer2" : [ "http://127.0.0.1:8044/" ] 209 // "peer2" : [ "http://127.0.0.1:8044/" ]
210 210
211 /** 211 /**
212 * This is another, more advanced format to define Orthanc 212 * This is another, more advanced format to define Orthanc
213 * peers. It notably allows to specify a HTTPS client certificate 213 * peers. It notably allows to specify HTTP headers, a HTTPS
214 * in the PEM format (as in the "--cert" option of curl), or to 214 * client certificate in the PEM format (as in the "--cert" option
215 * enable PKCS#11 authentication for smart cards. 215 * of curl), or to enable PKCS#11 authentication for smart cards.
216 **/ 216 **/
217 // "peer" : { 217 // "peer" : {
218 // "Url" : "http://127.0.0.1:8043/", 218 // "Url" : "http://127.0.0.1:8043/",
219 // "Username" : "alice", 219 // "Username" : "alice",
220 // "Password" : "alicePassword", 220 // "Password" : "alicePassword",
221 // "HttpHeaders" : { "Token" : "Hello world" },
221 // "CertificateFile" : "client.crt", 222 // "CertificateFile" : "client.crt",
222 // "CertificateKeyFile" : "client.key", 223 // "CertificateKeyFile" : "client.key",
223 // "CertificateKeyPassword" : "certpass", 224 // "CertificateKeyPassword" : "certpass",
224 // "Pkcs11" : false 225 // "Pkcs11" : false
225 // } 226 // }