Short note on :- 1) DIGITAL CERTIFICATE , 2) CERTIFICATION AUTHORITY (CA) , 3) THIRD-PARTY AUTHENTICATION
1) DIGITAL CERTIFICATE
- Electronic credentials are used to assert the online identities of individuals, computers, and other entities on a network.
- Function similarly to identification cards such as passports and driver's licenses. Most commonly they contain a public key and the identity of the owner.
- They are issued by certification authorities (CAs) that must validate the identity of the certificate-holder both before the certificate is issued and when the certificate is used.
- Common uses include business scenarios requiring authentication, encryption, and digital signing.
- Based on the X.509v3 certificate standard.
- Typically, digital certificates contain the following information:
- The subject’s public key value
- The subject’s identifier information, such as the name and email address
- The validity period (the length of time that the certificate is considered valid)
- Issuer identifier information
- The digital signature of the issuer, which attests to the validity of the binding between the subject’s public key and the subject’s identifier information
PROCESS TO OBTAIN DIGITAL CERTIFICATE
- One can obtain a certificate for your business from commercial CAs.
- The Issuing entities of commercial CAs provide certificates with a cost.
- Users can generate a Keypair of their own and generate a Certificate Signing Request (CSR) and then send the CSR to Issuing CA for a certificate.
- CSR contains the public key of the user and user identity information in a format that issuing CAs would normally expect as shown in the figure above.
2) CERTIFICATION AUTHORITY (CA)
- A Certificate Authority (CA) is a trusted institution/agent that issues digital certificates that contain a public key and the identity of the owner.
- The matching private key is not made available publicly but kept secret by the end-user who generated the key pair.
- The certificate is also a confirmation or validation by the CA that the public key contained in the certificate belongs to the person, organization, server, or other entity noted in the certificate.
- A CA's obligation in such schemes is to verify an applicant's credentials, so that users and relying parties can trust the information in the CA's certificates.
- CAs use a variety of standards and tests to do so. In essence, the Certificate Authority is responsible for saying "yes, this person is who they say they are, and we, the CA, verify that".
- If the user trusts the CA and can verify the CA's signature, then he can also verify that a certain public key does indeed belong to whoever is identified in the certificate.
- Browsers maintain a list of well-known CAs root certificates.
- Aside from commercial CAs, some providers issue digital certificates to the public at no cost.
- Large institutions or government entities may have their own CAs.
3) THIRD-PARTY AUTHENTICATION
- In third-party authentication systems, the password or encryption key itself never travels over the network. Rather, an "authentication server" maintains a file of obscure facts about each registered user.
- At the log-on time, the server demands the entry of a randomly chosen fact— the mother's maiden name is a traditional example—but this information is not sent to the server.
- Instead, the server uses it (along with other data, such as the time of day) to compute a token. The server then transmits an encrypted message containing the token, which can be decoded with the user's key.
- If the key was properly computed, the user can decrypt the message. The message contains an authentication token that allows users to log on to network services.
Comments
Post a Comment