When cloning databases from live to test sites, it is sensible to protect the live SF instance by overriding the "salesforce_endpoint" variable in settings.php. Unfortunately, this is inadequate to prevent a cloned site from connecting to the live SF instance, because the request for the Api endpoint doesn't actually us the endpoint variable. It instead uses the "salesforce_identity" struct variable. This can be cloned and re-used, producing undesirable corruption of live data from test sites.
Accessing the salesforce_identity variable should be shielded by validation against the current salesforce_endpoint.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | validate_identity_against_endpoint-2900041-6.patch | 945 bytes | gcb |
Comments
Comment #2
gcbComment #3
gcbImproved version to avoid edge case where update runs twice and actually CAUSES the issue we're trying to solve.
Comment #4
gcbImproved version that does not require an (unreliable) update or extra data to be stored in the identity variable.
Comment #5
gcbComment #6
gcbPrevious version was a little too picky as it includes the path for the allowed endpoint, which means a trailing slash (harmless in the config) can break the connection.
This version is more explicit and avoids this problem.
Comment #8
gcbComment #10
mariacha1 commentedI'm going to re-open so we can get the same functionality into D8. I'll add a patch back shortly.
Comment #11
mariacha1 commentedComment #13
aaronbaumanCommitted to 8.x-3.x