dannysummerlin / force-navigator

Force Navigator
MIT License
20 stars 6 forks source link

Issue still persistent. Works in dev org with more security settings, but not in sandbox/production with less security settings. Both use enhanced domain #31

Closed VAscendedSaiyan closed 1 year ago

VAscendedSaiyan commented 1 year ago
          Issue still persistent. Works in dev org with more security settings, but not in sandbox/production with less security settings. Both use enhanced domain

Sandbox/production does have a custom domain, but I made a CSP for the classic URL. Still no dice

DevOrg image

SandboxOrg image

Originally posted by @VAscendedSaiyan in https://github.com/dannysummerlin/force-navigator/issues/29#issuecomment-1531980605

TomHamiltonSmarsh commented 1 year ago

We are experiencing the same issue in our org.

spavuna-mle commented 1 year ago

Same. Any ideas @dannysummerlin?

dannysummerlin commented 1 year ago

Hi there, I've just moved countries so I'm behind on things. Can you try opening up the developer console while in the instance that is throwing errors and see if there are any messages that stand out as being errors from Salesforce Navigator? We'll have to recreate the issue to get to the bottom of it I'm afraid.

dannysummerlin commented 1 year ago

I'm merging this into #34, the short version is that the security features do block getting the token, the only way around that would be an extensive login handler that I won't be able to add, but I can restore all but the custom objects functionality, will be coming soon