Changes for page Sending certificates to a webservice

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-novice-securing-your-data-traffic-sending-certificates-to-a-webservice
	1	+novice-securing-your-data-traffic-what-are-certificates

Content

...	...	@@ -1,4 +1,9 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
	2	+
	3	+
	4	+
	5	+# What are certificates
	6	+
2	2	In this microlearning, we will focus on what certificates are and will relate this to how you could use them to secure your data traffic.
3	3
4	4	Should you have any questions, please contact academy@emagiz.com.
...	...	@@ -6,10 +6,10 @@
6	6	* Last update: April 22th, 2021
7	7	* Required reading time: 7 minutes
8	8
9		-== 1. Prerequisites ==
	14	+## 1. Prerequisites
10	10	* Basic knowledge of the eMagiz platform
11	11
12		-== 2. Key concepts ==
	17	+## 2. Key concepts
13	13	This microlearning centers around what are certificates.
14	14
15	15	By certificates we mean: A trustworthy document that is interchanged between parties to verify that both parties are who they claim to be
...	...	@@ -25,7 +25,7 @@
25	25
26	26
27	27
28		-== 3. What are certificates ==
	33	+## 3. What are certificates
29	29
30	30	In this microlearning, we will focus on what certificates are and will relate this to how you could use them to secure your data traffic.
31	31
...	...	@@ -42,7 +42,7 @@
42	42
43	43	* What are certificates used for?
44	44
45		-=== 3.1 What are certificates used for? ===
	50	+### 3.1 What are certificates used for?
46	46
47	47	One application of the use of certificates lies in the authentication. With certificates in this form, you have a method of verifying that the person that claims to be a certain individual is indeed that individual. One application lies in the encryption of data when it is being exchanged between two parties. This ensures that an independent third party cannot see what data is exactly exchanged between these two parties.
48	48
...	...	@@ -69,7 +69,7 @@
69	69
70	70	To recap, you have a server certificate (belonging to the party that receives the request) and you have a client certificate (belonging to the party that executes the request). With the help of a client certificate, a server can limit who can gain access to the server based on the certificate they provide at the door. If a server is publicly accessible but makes use of a certificate we say the connection is secured with the help of one-way SSL (HTTPS traffic). If the server requires a client certificate we talk about two-way SSL.
71	71
72		-=== 3.2 What if I want to use a self-signed certificate? ===
	77	+### 3.2 What if I want to use a self-signed certificate?
73	73
74	74	There is no technical requirement to always use certificates that are signed by a CA. Another approach is to create a self-signed certificate. This way the party that receives the request will look in the so-called truststore. The truststore houses all certificates (public keys) of trusted parties.
75	75
...	...	@@ -79,7 +79,7 @@
79	79
80	80	The combination of such a private key and a public key is called a key pair.
81	81
82		-=== 3.3 How to get your key signed by a trusted party ===
	87	+### 3.3 How to get your key signed by a trusted party
83	83
84	84	In some cases, an external party with whom we do business asks us to manage the certificate but has the requirement that the certificate that we have created and manage needs to be signed by a trusted party before it can be used in the field. To do you need to create a certificate signing request. You can do this with the help of tools such as Keystore Explorer, more on the technical details in a later microlearning.
85	85
...	...	@@ -87,17 +87,17 @@
87	87
88	88	After you have configured this correctly you should secure it via a password and save it. From here on you can create a certificate signing request (CSR). After a while, you will get a response back from the CA. You can link this to your keypair via an Import CA Reply. The result can be seen in Keystore Explorer.
89	89
90		-=== 3.4 Encryption ===
	95	+### 3.4 Encryption
91	91
92	92	To ensure encryption the client locks the data with the help of the public key in a format that can only be read by the intended party. At that point, only the party that has the matching private key has the option to decrypt the message and process it.
93	93
94	94
95	95
96		-== 4. Assignment ==
	101	+## 4. Assignment
97	97
98	98	Read up on certificates and how they work in communication with other parties and see if you get what the function of certificates is.
99	99
100		-== 5. Key takeaways ==
	105	+## 5. Key takeaways
101	101
102	102	* Certificates are all about trust
103	103	* When a certificate is trusted by a CA it is natively trusted by others
...	...	@@ -106,12 +106,13 @@
106	106
107	107
108	108
109		-== 6. Suggested Additional Readings ==
	114	+## 6. Suggested Additional Readings
110	110
111	111	If you are interested in this topic and want more information on it please read the release notes provided by eMagiz
112	112
113		-== 7. Silent demonstration video ==
	118	+## 7. Silent demonstration video
114	114
115	115	{{video url="https://youtu.be/7TxZGQKXZnQ" attachment="Certificates * The Adventure" videoPoster="http://i.imgur.com/Ot5DWAW.png"/}}
116	116
117	117	)))((({{toc/}}))){{/container}}{{/container}}
	123	+