You need to sign in to do that
Don't have an account?
RalphCallaway
Trapdoor Fails Silently Consistently for Certain Orgs
I use trapdoor for a ton of different orgs. I've run into an issue now for two orgs where when I login nothing happens. I don't get an error message that the crendentials are expired and the browser doesn't open.
It's fairly rare, but it happens 100% of the time for these orgs. Login history in salesforce shows a successful login from Trapdoor.
I've tried deleting the credentails directly from Trapdoor, and also from KeyChain. But I still have the same issue after I add the credentials back to Trapdoor.
Anyone encountered this and have suggestions for a fix? Is there any logging done by trapdoor that can be used to troubleshoot?
It's fairly rare, but it happens 100% of the time for these orgs. Login history in salesforce shows a successful login from Trapdoor.
I've tried deleting the credentails directly from Trapdoor, and also from KeyChain. But I still have the same issue after I add the credentials back to Trapdoor.
Anyone encountered this and have suggestions for a fix? Is there any logging done by trapdoor that can be used to troubleshoot?
@ralphatccc Also make sure you have the latest version as that’s the only one with the TLS 1.2 support in it.
@ralphatccc v1.10
Confirmed v1.10. Console logs show trapdoor is getting an unexpected response from salesforce, not sure why.
perhaps 302 redirects could just be ignored? or is there a cookie cache somewhere that could be cleared so salesforce doesn't redirect to mydomain unless the request is truly for that org?
redacted log, important things to note "<redacted_org_id>" is for the target org, but the "<redacted_my_domain>" is for a different org id on the same data center/pod. so it doesn't make any sense for https://na22.salesforce.com/services/Soap/u/17.0/<redacted_org_id>, to redirect to https://<redacted_my_domain>.my.salesforce.com/services/Soap/u/17.0/<redacted_org_id>