Changes for page SFTP Known Hosts

Summary

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

Details

Page properties

Content

...	...	@@ -25,6 +25,22 @@
25	25
26	26	There are two distinct ways of retrieving and storing the unique fingerprint of the SFTP in a "known hosts file". The first option is portal based and the second option is command line based. The preferred option is the portal based one. Do note that the first option only works if the SFTP is **publicly** accessible without any IP restrictions.
27	27
	28	+=== 3.1 Known Hosts File Generation - Portal ===
	29	+
	30	+=== 3.2 Known Hosts File Generation - Command Line ===
	31	+
	32	+The secondary option, when there are IP restrictions, provides you with the option to execute several commands after gaining access to the correct server to generate the known hosts file. These steps are detailed below.
	33	+
	34	+* Gain access to the server in question from which you can reach the SFTP.
	35	+* Execute the following command (compatible with both Linux and Windows): {{code}}ssh-keyscan -p [port] [host] > [known-hosts target path]{{/code}}
	36	+** An example would be: {{code}}ssh-keyscan -p 22 localhost > C:\tmp\generated_known_hosts{{/code}}
	37	+* Navigate to the generated file and open it. The file should contain one or more lines in the format {{code}}hostname/ip key-type value
	38	+e.g. 127.0.0.1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAICZPI5pQ6PSXgS4QOPsai2QjC2EcVjFejvUM5RMYOmwbwW{{/code}}
	39	+* Open eMagiz and navigate to the flow where the file is needed.
	40	+* Upload the known_hosts file as a flow resource, and click on the "eye" icon to see its unique name.
	41	+* Define a property for the known hosts field in the SFTP (caching) session factory.
	42	+** Provide a value for the property upon deploying the release that follows the following structure: {{code}}classpath:emagiz-resources/[filename]{{/code}}
	43	+
28	28	If you are looking for some introductory reading into certificates, please check this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Securing Data Traffic.novice-securing-your-data-traffic-what-are-certificates.WebHome||target="blank"]].
29	29
30	30	As the private key is yours, you can ask a trusted party to generate the key, or you could create it yourself. The latter part happens a lot when connecting to an SFTP. You could use a tool like PuttyGen to achieve this. As a result, you will have a keypair. The private key should be kept safely with you in eMagiz, and you need to share the public key with the SFTP server party. In this microlearning, I will not explain how PuttyGen works in detail. Instead, we will focus on the part in eMagiz. In eMagiz, we need to refer to the key file (linked under Resources), and we need to refer to the password we use to save our key file securely.