I execute “sail api get /v2025/transforms“ fail.The reason is below
I have check clientId and clientSceret by powershell and get accessToken successfully.the script is below
getHeader.ps1 (875 Bytes)
the accessToken:
I don’t know what reason cause this error happen.How do I solve this problem
Have you tried running sail command(s) from a standard Command Prompt? Do you have the correct Environment setup? Try sail env show
Are you using a PAT for connection?
I am able to issue sail api get /v2025/transforms from both a Command prompt and Powershell ISE prompt.
I noticed in your screenshot that the error message is “TLS handshake timeout.”
This looks like a network-related issue.
Could you please check whether you’re able to ping or otherwise reach the SailPoint API from your environment ?
the above is environment setup,I use PAT for connection and I can get accessToken by powershell script.
And port 443 is open ?
if you have openssl, you can try : openssl s_client -connect your_api_url:port
execute “openssl s_client -connect your_api_url:port “ in VA?
not in VA but In your current environment where you try to use the cli.
The cli already work, but your initially error message : “TLS handshake timeout.” is probably link to network issue.
Do you already have an API client, like postman in the same environment where you use the cli ?
Seems like port also is opened.
You can try to install the cli in the same environment where you already use API clients (like Postman).
Shall I use Invoke-RestMethod to use API in powershell?
You can try it, but the “TLS handshake timeout” issue is coming from your current environment.
For example, instead of using your IQService server, you can install the CLI directly on your laptop.
If that works, you can then check everything related to certificates on your IQService server.
I can call api by powershell.
I can call api by cli tool in my laptop but fail in lab IQService.
In my laptop:
In lab IQService:
That typical mean your IQService lab have some network issue.
But error message mentionned in your screenshot is different from the initial message error from your first post ?
