Issue with new SaaS conn source

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

I have successfully created/deployed several SaaS Conn connectors in the past few month but running into issue with the latest one.
I am able to test fine locally but when trying to test with the same token (same config.json) in the tenant I am running into error indicating that token is incorrect. I have checked and service that I am calling does not block/distinguish between external clients (in fact I have called fine from my computer at home). I tried deleting and recreating this connector…looking for any advise on what else I can do?

Here is the results of deploying and testing connector in the tenant:

> [email protected] prebuild
> npm run clean


> [email protected] clean
> shx rm -rf ./dist


> [email protected] build
> npx ncc build ./src/index.ts -o ./dist -m -C

ncc: Version 0.34.0
ncc: Compiling file index.js into CJS
ncc: Using [email protected] (local user-provided)
   0kB  dist/file.js
   1kB  dist/worker-pipeline.js
   1kB  dist/worker.js
   5kB  dist/worker1.js
1609kB  dist/index.js
1616kB  [3541ms] - ncc 0.34.0

> [email protected] prepack-zip
> npm ci && npm run build

npm WARN deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
npm WARN deprecated [email protected]: Use your platform's native DOMException instead
npm WARN deprecated [email protected]: Use your platform's native performance.now() and performance.timeOrigin.

added 495 packages in 3s

49 packages are looking for funding
  run `npm fund` for details

> [email protected] prebuild
> npm run clean


> [email protected] clean
> shx rm -rf ./dist


> [email protected] build
> npx ncc build ./src/index.ts -o ./dist -m -C

ncc: Version 0.34.0
ncc: Compiling file index.js into CJS
ncc: Using [email protected] (local user-provided)
   0kB  dist/file.js
   1kB  dist/worker-pipeline.js
   1kB  dist/worker.js
   5kB  dist/worker1.js
1609kB  dist/index.js
1616kB  [3920ms] - ncc 0.34.0

> [email protected] pack-zip
> spcx package

Connector zip file created under dist folder: r2-idn-connector2-0.1.0.zip
+--------------------------------------+---------+
|             CONNECTOR ID             | VERSION |
+--------------------------------------+---------+
| 5e01ac94-5efb-411d-bd37-62be4864d95a |       1 |
+--------------------------------------+---------+
CYT6Q4QFVT:r2-idn-connector ralph.mishiev$ sail connectors invoke test-connection -c r2-idn-connector2 -p config.json
2024/01/04 09:57:27 Running "std:test-connection" with "{}"
Error: non-200 response: 400 Bad Request (body {
        "detailCode": "Bad Request",
        "messages": [
                {
                        "locale": "en-US",
                        "localeOrigin": "DEFAULT",
                        "text": "[ConnectorError] Failed in testConnection: Error \"Request failed with status code 403\""
                }
        ],
        "trackingId": "3f3eaa8c7fe34d03a2721ca24e4bf467"
})
2

I did more debugging and the error 403 happens when service do not see our custom authorization header. When I added Axios interceptors.request in the code deployed to tenant I can see in the logs, headers are being generate/sent from the tenant but somehow service does not get them. Is there any sort of proxy in the SaaS Conn infrastructure that may be stripping headers?
(Note: as I have mentioned before new connector code that failing in tenant works fine locally)

3

I am not aware of anything in SaaS connectivity that would be stripping your headers. Is it possible that there is some kind of origin policy on this custom endpoint you are accessing?

4

Thanks for suggestion, we are currently looking to see if there is anything on on our network path in front of the service can trigger 403.

5

Issue was resolved, issue was related to resent updates to firewall in front of the service.

6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.