Timeline for Whitelisting Salesforce IP In External Systems
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2019 at 8:34 | comment | added | Salvation | Thanks! that helped me a lot. | |
| Aug 8, 2019 at 8:34 | vote | accept | Salvation | ||
| Aug 8, 2019 at 8:07 | comment | added | salesforce-sas | As you pointed in your question, there are 1M+ IPs, thats big disadvantage. For this encryption, you can create utils class (thats what we did in a project). You can check for other potential solutions, but we found this to be least effort and best results. | |
| Aug 8, 2019 at 8:04 | comment | added | Salvation | Hi, What are the disadvantages of using this work-around solution over the IP check? Except for the reason that we both should add some code to encrypt and decrypt the Key...One more thing - The External Service that I'm working with, said that they identify by IP or by Header Key/Value - and that why I asked about sending a key via the Header. Can I use your method to encrypt a key and send it in the Header as a key-value to Identify? I believe that the limitation on the header will need to check also in this case. Thanks a lot. | |
| Aug 8, 2019 at 8:03 | comment | added | salesforce-sas | If you are sending the key direcly, anybody who is able to read the request in middle will be able to decode the body. Try to speak with them and say its a 1 time key which can be saved in their server. This is how its done for many integrations (for sensitive data) | |
| Aug 7, 2019 at 9:19 | history | answered | salesforce-sas | CC BY-SA 4.0 |