With SOAP login() set to be depreciated,
I am starting to look for new ways to authenticate myself to Salesforce. I need this to work more or less headlessly for at least two integration developers (e.g. no web login page).
What I mean by this is, for Soap Login, if there is a reset in security token, all I need to do is to update the security token once in code configuration.
I looked at External Apps and I found that
- External App Client Credentials: This is now disabled on newer versions of External Apps (the only way to do this is to enable Connected App I think, which is basically replacing one depreciation for another depreciation).
- External App JWT method: Would work, but this does not prevent developer A from impersonating as developer B (unless I create N number of External App), and also need to maintain certificates somewhere.
- Refresh Tokens technically require only one human interaction each time the refresh token expires (e.g. similar to security tokens). But I can't really tell how long access tokens last and under what conditions do refresh token expire.
2 respuestas
