Help Me With Install eSignature in SalesForce

Help Me With Install eSignature in SalesForce

how does HTTP work I'm planning on releasing a couple of new videos on securing micro-services with HTTPS and also about how you can use kubernetes to automatically obtain the TLS certificates required for HTTPS and for that I think it makes sense if everyone understands how HTTPS works this video won't get too technical I've simplified a couple of concepts so it will fit in a shorter video so after the end of this you might not be able to implement all the required algorithms from scratch but you should be able to understand how the common tools that are out there what they do and how you can use them to implement HTTPS protection for your micro services oftentimes I've experienced that developers treat this whole HTTP communication thing as that sort of black box they don't even want to try to understand because it sounds so complicated but it's actually pretty simple and I'd like to show you just how it works with this video so let's start with a couple of prerequisites whenever you hear HTTP and there's cryptography involved it almost sounds very complex and very mathematical but it doesn't really have to be complex at all you just need to trust that public key cryptography and signature works now if you're saying what is public key cryptography and signature it's basically a couple of very simple mathematic functions that only work in one way or that are much easier to compute in one way than in another way but you should trust these two principles you should trust that any message that has been encrypted with Bob's public key and Bob's public key is public it's out there for everyone can only be decrypted with Bob's private key so basically that means only Bob because he's the only owner of his private key can decrypt this message even though it can be publicly distributed and everyone can listen to it but no one can do anything with it because they just see some random bytes so that was the public key cryptography part and then there's also the signature part so anyone who is access to Alice's public key can verify that a message could only have been created by someone with access to Alice's private key so basically this means anyone on the Internet even though they don't know Alice's private key only Alice knows her private key can verify that a message was actually sent by Alice and in the background there's basically just a bit of multiplication and modulus calculation going on but you don't have to worry about that at all just take this as given based on this we can now start with your browser and let's say you want to access youtube.com so the first thing your browser does it tells the internet give me youtube.com this is of course very simplified in a background there'll be DNS requests going on so you can resolve that name to...