search

lispercat / sailpoint-iiq-dev-accelerator

VSCode extension to accelerate and facilitate development by directly interacting with the target Sailpoint IIQ server
MIT License
30 stars 11 forks source link

Post request failed with FetchError: request to https://MY-IIQ-URL:8443/identity/rest/workflows/IIQDevAcceleratorWF/launch failed, reason: self signed certificate #18

Closed martinwoit closed 3 years ago

martinwoit commented 3 years ago

Hey, many thanks for the extension!

Currently I'm trying to connect but it fails due to the self signed cert. Is there a possibility to have a setting to ignore certificate issues?

Post request failed with FetchError: request to https://MY-IIQ-URL:8443/identity/rest/workflows/IIQDevAcceleratorWF/launch failed, reason: self signed certificate

Thank you in advance, Martin

martinwoit commented 3 years ago

temp solution:

~/.vscode/extensions/andreistebakov.sailpoint-iiq-dev-accelerator-1.0.27/out/commands.js

uncomment line 336 to process.env.NODE_TLS_REJECT_UNAUTHORIZED = 0;

Save file. Restart VSCode.

lispercat commented 3 years ago

Thanks, Martin, for using the plugin! You are exactly right about your workaround. In the code takes care of unauthorized certificates by creating this agent: const agent = parsedUrl.protocol === 'https:' ? new https.Agent({rejectUnauthorized: false}):new http.Agent();

The thing with VSCode is that it itself is in a constant flux and I had cases when this agent stopped working with some new update and then started working again :) The process.env.NODE_TLS_REJECT_UNAUTHORIZED = 0; is a little more "drastic" solution but it works too (that's why I kept it commented out just in case). Let's watch this issue for some time, good that you found the fix!

On Tue, Nov 2, 2021 at 4:42 PM Martin Woit @.***> wrote:

Closed #18 https://github.com/lispercat/sailpoint-iiq-dev-accelerator/issues/18.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/lispercat/sailpoint-iiq-dev-accelerator/issues/18#event-5558150664, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACCZB2AYHPNTW2CEXQB67TUKBEKZANCNFSM5HF45BUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

kgknox27 commented 2 years ago

Hi,

Apologies I know this issue is closed. I had this and previously used the work around described by @martinwoit to fix this for my sandbox. However, after upgrading to the most recent version (jan 6) it is broken for me again. I went back into the file and noticed line 336 was commented out again. I uncommented and reloaded vscode but I am still getting the issue. Any ideas?

ghost commented 2 years ago

Uncomment the one in andreistebakov.sailpoint-iiq-dev-accelerator-1.0.31/client/out/commands.js

lispercat commented 2 years ago

I used to have that issue before when I upgraded to some new version of VSCode, but I haven't seen that issue for a while. Guys, if you like I can create a config variable that would keep the line of code enabled if the variable is set. This way you won't have to modify the code with every new upgrade.

On Wed, Jan 12, 2022 at 12:21 PM Mark Earnest @.***> wrote:

Uncomment the one in andreistebakov.sailpoint-iiq-dev-accelerator-1.0.31/client/out/commands.js

— Reply to this email directly, view it on GitHub https://github.com/lispercat/sailpoint-iiq-dev-accelerator/issues/18#issuecomment-1011278903, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACCZB5R5KDOKCC3AVBRRUDUVW2CNANCNFSM5HF45BUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

lispercat commented 2 years ago

I released 1.0.32 which has a config variable iiq-dev-accelerator.disableTLSValidation. If you set it to true, the NODE_TLS_REJECT_UNAUTHORIZED will be set to 0.

On Wed, Jan 12, 2022 at 12:31 PM Andrei Stebakov @.***> wrote:

I used to have that issue before when I upgraded to some new version of VSCode, but I haven't seen that issue for a while. Guys, if you like I can create a config variable that would keep the line of code enabled if the variable is set. This way you won't have to modify the code with every new upgrade.

On Wed, Jan 12, 2022 at 12:21 PM Mark Earnest @.***> wrote:

Uncomment the one in andreistebakov.sailpoint-iiq-dev-accelerator-1.0.31/client/out/commands.js

— Reply to this email directly, view it on GitHub https://github.com/lispercat/sailpoint-iiq-dev-accelerator/issues/18#issuecomment-1011278903, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACCZB5R5KDOKCC3AVBRRUDUVW2CNANCNFSM5HF45BUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>