force-dot-com-esapi
force-dot-com-esapi copied to clipboard
Enterprise Security API for the Apex language on the Force.com platform.
This PR will resolve the possibility for an attacker to perform an **Open-Redirect** attack on the JavaDoc.
API version of many Apex classes is 29.0, can they be updated to 58.0 or 59.0 to avoid them been flagged by some security tools?
* Created a factory * Created base class [virtual] to remove some redundancies (when only with, without, etc. is needed) * Retained Operation Modes for factory create ( to reduce...
This is not an issue but a query. How can we test for upsert operation? I found method for insert/update and delete but not sure how to check for upsert
The SFDCAccessControlException wasn't setting the exception message. This resulted in the message being 'Script-thrown exception'. Explicitly call the Exception constructor to set the message with useful details.
Create a decoder class Add the base 64 url decode feature on it Add a link to the easpi class Add the test class