Getting "Unable to get IP for provided target host" with basic auth authentication

Genesys Cloud Integrations
1

Hi ,

1)we have set up an web service data action integration using using basic AUTH method (giving user name and password)
2) Above integration is used to create a data action that send a post request to our oauth endpoint and the output is a bearer token in return. till here things are working fine
3) Now we want to use this token to send a "get" request to our api end point which will return certain response such as dateofbirth.. For this we have created a data action (integration used is same as in point 1) and we have provided the url and authorization but on test of data action we are getting below error:-

Error running action test
8. Execute: The request could not be understood by the server due to malformed syntax.
Unable to get IP for provided target host. Host attempted: i**p-*..com
JSON
{
"message": "The request could not be understood by the server due to malformed syntax.",
"code": "bad.request",
"status": 400,
"messageParams": {},
"contextId": "386ac293-5463-44db-93e9-79a0c5cddcd7",
"details": [
{
"errorCode": "ACTION.PROCESSING"
}
],
"errors": [
{
"message": "Unable to get IP for provided target host. Host attempted: -test.**.com",
"code": "BAD_REQUEST",
"status": 403,
"messageParams": {},
"details": [],
"errors": []
}
]
}

2

Hi Garima,

It looks like the custom Oauth credential type and authentication data action will be great for what you are trying to do:

I don't know why you would be getting this error " Unable to get IP for provided target host. Host attempted: i**p-* . .com" other than having that in your "Request URL Template".

--Jason

3

Hi Jason ,
Authentication method implemented by our client is "basic auth". Hence pointing my data action to same integration.

Attaching the snapshot for better reference.

image
image1213×832 27.1 KB

4

Hi Garima,

Please attempt to do a DNS lookup of the host that you are attempting to use on a public DNS lookup web site, like https://mxtoolbox.com/ You may be using a host that you can get to on your corporate network, but does not have a public DNS record.

If your workflow is

  1. Call an endpoint with basic auth to get an authorization token
  2. Call the endpoint providing the authorization token in order to do useful work

Then you are going to want to use the "Custom Oauth" information that I provided above.

--Jason

5

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