Skip to main content
Information Security

Return to Answer

the operation executed with the private key is called "sign"
Source Link
edit approved Jan 17, 2014 at 10:51
Community Bot
edit approved Jan 17, 2014 at 10:51
Community Bot
  • 1

From a high level perspective, three things have to happen:

  1. The client has to prove that it is the proper owner of the client certificate. The web server challenges the client to encryptsign something with its private key, and the web server validates the response with the public key in the certificate.

  2. The certificate has to be validated against its signing authority This is accomplished by verifying the signature on the certificate with the signing authority's public key. In addition, certificate revocation lists (CRLs) are checked to ensure the cert hasn't been blacklisted.

  3. The certificate has to contain information which designates it as ana valid user of the web service. The web server is configured to look at specific items in the certificate (typically the subject field) and only allow certain values.

From a high level perspective, three things have to happen:

  1. The client has to prove that it is the proper owner of the client certificate. The web server challenges the client to encrypt something with its private key, and the web server validates the response with the public key in the certificate.

  2. The certificate has to be validated against its signing authority This is accomplished by verifying the signature on the certificate with the signing authority's public key. In addition, certificate revocation lists (CRLs) are checked to ensure the cert hasn't been blacklisted.

  3. The certificate has to contain information which designates it as an valid user of the web service. The web server is configured to look at specific items in the certificate (typically the subject field) and only allow certain values.

From a high level perspective, three things have to happen:

  1. The client has to prove that it is the proper owner of the client certificate. The web server challenges the client to sign something with its private key, and the web server validates the response with the public key in the certificate.

  2. The certificate has to be validated against its signing authority This is accomplished by verifying the signature on the certificate with the signing authority's public key. In addition, certificate revocation lists (CRLs) are checked to ensure the cert hasn't been blacklisted.

  3. The certificate has to contain information which designates it as a valid user of the web service. The web server is configured to look at specific items in the certificate (typically the subject field) and only allow certain values.

Source Link
John Wu
John Wu
  • 9.4k
  • 2
  • 31
  • 40

From a high level perspective, three things have to happen:

  1. The client has to prove that it is the proper owner of the client certificate. The web server challenges the client to encrypt something with its private key, and the web server validates the response with the public key in the certificate.

  2. The certificate has to be validated against its signing authority This is accomplished by verifying the signature on the certificate with the signing authority's public key. In addition, certificate revocation lists (CRLs) are checked to ensure the cert hasn't been blacklisted.

  3. The certificate has to contain information which designates it as an valid user of the web service. The web server is configured to look at specific items in the certificate (typically the subject field) and only allow certain values.