Function: putCert
Use
Effect
The client certificate and a client identification ( authId) are transferred.
The client certificate (see secKey) is decoded in the message body and transferred in binary format.
For reasons of security, it is recommended that it be made mandatory for an administrator to perform some kind of manual action after the certificate has been transferred, before access is actually allowed. This could be a public key fingerprint check or any other plausibility check.
The logon procedure therefore consists of two steps:
-
The certificate is transferred and entered in a central location.
-
An administrator uses a tool to grant access.
After the first step of this procedure, the certificate is created, but access has not yet been granted. The client only gains access after the second step of the procedure.
Access Mode
-
Client -> Server
The client sends an HTTP-Put-Request.
|
Parameter |
Optional/Mandatory |
Sign |
|
authId |
Mandatory |
|
|
pVersion |
Mandatory |
|
|
contRep |
Mandatory |
The certificate is transferred in the request body. All the other parameters are transferred in the URL. The URL does not contain a secKey.
Server -> Client
The server answers the request with a response. The response status code indicates the outcome of the call.
|
HTTP Status Code |
Meaning |
|
200 (OK) |
OK |
|
400 (bad request) |
Unknown function or unknown parameter |
|
406 (not acceptable) |
Certificate not recognized |
|
500 (Internal Server Error) |
Internal error on Content Server |