Archer SaaS & CORS
We're entertaining the idea of moving to Archer SaaS. But we have some custom Ajax components that we use in Archer to call services back at our home office. If we decided to go SaaS, would our Ajax calls start failing because of CORS? I'm thinking they would because the SaaS instance and our services would no longer be on the same domain.
It's true that they would both be in different domains, but it really depends on what you're doing in your calls as to whether we can make it work. It's possible that it can be accomplished, just in another way. I'd suggest contacting your account team, who can initiate general fact finding calls, engaging the appropriate RSA associates to get you more specific answers.
Love that you're looking at RSA Archer SaaS!
Adding onto this question as it's been a little time.
Has anyone successfully made jQuery/Ajax POST calls from custom objects within Archer SaaS to resources that are outside of the Archer SaaS domain? We've been receiving some conflicting answers to this from folks so we wanted to check with the masses. A straight Ajax POST call to a resource on a different domain should cause the call to fail because of CORS, so we wanted to check.
Thanks in advance!