I am looking at connecting two Salesforce organizations. The issue we are running into, is what these two organizations have access to needs to be completely separate.
We don't want to store login information in one organization, to connect to the other organization.
I was thinking of creating a lightweight REST Api to perform the one specific function we are trying to accomplish.
The organization can then do a Callout to this REST Api to do this specific function on the other organization.
The challenge is around authentication. If I go the standard OAUTH route, then I need a user and I have to worry about the different profile level security etc etc. Then this login information is stored as well.
What if I just create a token that is required in the Rest APEX class, that you cannot use the APEX class without. Then I could make this APEX class public and forgo the OAUTH.
Would this be an absolutely horrible idea? Maybe I'm missing something here.