18.04.2013 Views

B2B Integration : A Practical Guide to Collaborative E-commerce

B2B Integration : A Practical Guide to Collaborative E-commerce

B2B Integration : A Practical Guide to Collaborative E-commerce

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

300 <strong>B2B</strong> <strong>Integration</strong> — A <strong>Practical</strong> <strong>Guide</strong> <strong>to</strong> <strong>Collaborative</strong> E-<strong>commerce</strong><br />

10.6.6. Digital certificates and role of Certificate<br />

Authorities (CAs)<br />

All of the above mechanisms of security relied on using public keys<br />

and private keys for both the sender and the receiver. The question<br />

arises — where do these keys come from? How does the outside world<br />

get hold of the public key of a particular party?<br />

The answer lies in digital certificates, issued by organizations called<br />

Certificate Authorities (CAs). Certificates can be used <strong>to</strong> replace passwords<br />

and login ID's wherever access is <strong>to</strong> be restricted <strong>to</strong> certain<br />

users, such as registered cus<strong>to</strong>mers. In several applications, certificates<br />

may replace 'cookies', which have proven unpopular with many Web<br />

users.<br />

Any company/individual wishing <strong>to</strong> communicate securely over the<br />

Internet can apply <strong>to</strong> a CA for a digital certificate. It has <strong>to</strong> send<br />

its identification information and public key <strong>to</strong> the CA. The CA will<br />

verify the authenticity of information and then issue a certificate with<br />

the given information and public key. To seal the certificate, the CA<br />

encrypts it with its private key and sends it <strong>to</strong> the applicant (see<br />

Figure 10.9).<br />

In this approach, when Company A wants <strong>to</strong> communicate with<br />

Company B, it will ask Company B for its certificate. On receiving this<br />

certificate, Company A will decrypt the same using the CA's public key.<br />

It will then read the identifying information on the certificate. If satisfied,<br />

it will use the public key present on the certificate <strong>to</strong> send across the<br />

information <strong>to</strong> Company B.<br />

This methodology is not only secure, but requires the sender <strong>to</strong><br />

know only the CA's public key, rather than remember the public key of<br />

every party it wishes <strong>to</strong> communicate with.<br />

The most widely recognized standard public key certificate format is<br />

defined in the ITU X.509 standard.<br />

Serial<br />

Number<br />

Signature<br />

N umber<br />

CA Info<br />

CA<br />

Number<br />

Owner Info<br />

Owner's<br />

N umber<br />

Owner's<br />

Public Key<br />

N umber<br />

Validity<br />

Period<br />

Figure 10.9. — Simple public key certificate<br />

CA<br />

Digital<br />

Signature

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!