New SailPoint VA deployed - Test Connection to Source

[swapnasarit (Swapnasarit Panda)]

Hi Team,

I encountered an issue while testing the Virtual Assistant (VA) deployment process with the recent changes for generating keyPassphrase (using va-bootstrap set-passphrase -t internal).

Following the steps outlined in the configuration page, I successfully deployed and configured the VA and verified that all services were running.

However, when attempting a test connection for a connected source, I received the following error: DelegatedAmazonCredentials.

Please find the attached screenshot for reference.

Note: I am using a demo tenant for this testing.

Could someone please assist me in resolving this issue?

Thank you

[JackSparrow (Theja C)]

Hi @swapnasarit

Its “401 unauthorized error”. Credentials that you are using for connection is incorrect. Please have a check.

[swapnasarit (Swapnasarit Panda)]

Hi @JackSparrow

Thank you for your response.

I agree with you.

But I am trying to connect to a webservice application. When I use the Web service Connector(which uses VA) I get this error. However, I checked by using the Web Service SaaS Connector where I got my test connection successful. Which means, my credentials are correct.

[JackSparrow (Theja C)]

Strange. Credentials should work for all. Can you check if the same credentials you are using for web services works in Postman?

[Santhakumar (Shantha Kumar)]

Can you try the curl or nc command to check whether the connection is established from VA to the source??

[officialamitguptaa (Amit Gupta)]

@swapnasarit -

For registering the VA, for the demo tenant below command must be used -

va-bootstrap set-passphrase -t demo → The tenant argument should be demo

Why are you passing the tenant argument as internal???

Thank you!

[swapnasarit (Swapnasarit Panda)]

@officialamitguptaa

Yes, I initially used the same command, but it did not work. I then tried the new command provided within the cluster configuration.

However it is now functioning correctly with the -t demo command only.

I suspect this failure might have been caused by a temporary downtime issue.