Apex Code Development You need to sign in to do that
Don't have an account?
API key - SOAP whitelisting inconsistency
Hi everyone and thanks in advance for reading.
We provide a managed package that needs access to the SOAP API from our server to perform CRUD operations on objects. We use the Salesforce user's session ID to authenticate, and our package is whitelisted through an API key so that everything works automatically in Group- and Professional-Edition orgs.
Our problem is that this approach doesn't work in other org types: a user lacking the explicit "API Enabled" setting cannot use our product in spite of the same API key that works just fine in Group/Professional.
This is a potential problem in a couple of our customers' community implementations, because our current best option (asking the customer to set "API Enabled" for the users concerned) would be bad practice. Can anyone advise on alternative approaches to support these users?
regards,
Jim
We provide a managed package that needs access to the SOAP API from our server to perform CRUD operations on objects. We use the Salesforce user's session ID to authenticate, and our package is whitelisted through an API key so that everything works automatically in Group- and Professional-Edition orgs.
Our problem is that this approach doesn't work in other org types: a user lacking the explicit "API Enabled" setting cannot use our product in spite of the same API key that works just fine in Group/Professional.
This is a potential problem in a couple of our customers' community implementations, because our current best option (asking the customer to set "API Enabled" for the users concerned) would be bad practice. Can anyone advise on alternative approaches to support these users?
regards,
Jim
visit: reviews & ratings of mowers (https://wowconsumers.com/best-riding-lawn-mower/)