To connect to SSO protected Appian environment from SoapUI

Are you getting *no* response, or something like a 401 error?

Hi Philb , I am getting no response.

I can see the below error in the error log :
ERROR:Exception in request: javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name

Does this help? stackoverflow.com/.../soapui-fails-to-connect-https-sslpeerunverifiedexception

Yes Philb , I checked and added the -Djsse.enableSNIExtension=false to the SoapUI-5.2.0.vmoptions. But after adding it , the handshake error has been resolved, But I couldn't get the expected response. The response posses the tag <title>Loading ...</title> and <script> tag the SSO authentication details. I couldn't get the actual body response.

There's nothing else in the response except that tag? Presumably you're passing both a username and password to the service, and have selected http basic authentication within SoapUI? Are you able to share a redacted version of the URL that you're using?

The body response is as below ,
^\(^\)]*$/; if (sSource.length > 0 && !regExp.test(sSource)) { return false; } return true; } function iwaTestResult(canGo) { if (canGo) { document.location.replace(dssoRedirectUrl); } else { document.location.replace(siteMinderFormsUrl); } } function sreplaceAll(source, stringToFind, stringToReplace) { var temp = source; var index = temp.indexOf(stringToFind); while (index !== -1) { temp = temp.replace(stringToFind, stringToReplace); index = temp.indexOf(stringToFind); } return temp; } })();

That does look like it's getting caught by CA siteminder... What does your URL look like? It should be something like https://<environment>/suite/webapi/<webapiname>

I'm able to call a webapi that's behind SSO without issue, but I guess your configuration could be different.

Hi Philb ,I am not passing the credentials other than through http basic authentication. I am confused since the response remains same in both basic Authentication is provided or not provided .(But I have logged in to SSO to my Appian environment in IE)

The URL will be like,
https://(environment).(bankid)/suite/webapi/testRunStatusForId?id=1

Also Could You please help me with the steps you are following in SOAPUI.

Since I have queries like where to provide the SSO credentials and Should we need to provide proxy details etc...

Ok, so your URL should be similar to what you've posted but without the querystring on the end - in SoapUI that should be added as a parameter (you might already be doing that). For auth, you should select Basic and populate the Username and Password fields, and select "Authenticate pre-emptively".

If you're already doing the above and you're still getting the issue, I suspect it's down to your SSO configuration, so you should either speak to whoever configured the SSO or alternatively raise a support case - probably the former.

Since the auth settings in SoapUI can be a bit hard to find, I've attached a screenshot. Note that you have to click the Auth label before this dialogue is shown.

Thank You so much for you quick and detailed response Philb. Yes I have followed the same way for providing the Authentication and I too had a guess on SSO. Could you please help me with little more deep details about the SSO like the issue you faced due to SSO and the factors that helped you to resolve the issue.

I have taken a work around to exclude “/suite/webapi/testRunStatusForId” resource from SSO protection. Is this a right way ?

Thanks :)

Thank You so much for you quick and detailed response Philb. Yes I have followed the same way for providing the Authentication and I too had a guess on SSO. Could you please help me with little more deep details about the SSO like the issue you faced due to SSO and the factors that helped you to resolve the issue.

I have taken a work around to exclude “/suite/webapi/testRunStatusForId” resource from SSO protection. Is this a right way ?

Thanks :)

Hi,

I think it might be due to SSO. Create a basic user and provide viewer rights for webapi. Invoke with the basic user credentials,It will work as expected.

Hi Swapna,

Thanks for the suggestion. But I have tried by providing admin rights to my user profile and Invoked it from my credential. Though I am getting 403 Forbidden error.

If you have achieved this through SSO , could you please share me the issues faced and their solutions. If no issues , have you changed any security in SSO for calling webApi from external tools. Kindly help me out.

Thanks in advance.

Hi,

Since your profile is configured with SSO, you can't call the service even though you have administrator rights, So, create a new basic user and provide viewer access. Use the same credentials of new user during authentication in SOAP UI, it will work.

Hi Swapna,

Great. The environment in which I was getting 401 unauthorized error , I tried you solution and now I am getting 403 Forbidden error. I hope one issue was solved but struck with one other issue.

Could you please suggest any solution for this error.

Thank you.

Hi Prakash,

AFAIK, 403 might be your network domain will not allow other networks to access it. If possible please try to invoke from different external systems such as (POSTMAN,SOAP UI or https://www.hurl.it) and check the response. Still facing issues, attach screenshot of error which will help to debug further.

Hi Swapna,

Thanks for you suggestion. Actually I tried it testing through SOAP UI and getting the same 403 Forbidden Error. I have attached the snapshot for your reference. Kindly check if its helps or let me know if you need any further information,

Thanks and Regards,

Guru

Hi,

In this case, 403 means your authentication is successful but you are not authorized to access the resource. Could you please check, for the user whether you have proper access to the resource which you are fetching data ?

Hi Swapna,

As you suggested earlier, I provided viewer access for a Basic User id and tested with the same credentials in SoapUI. Adding to it ,if I remove the authentication details also it's throwing the 403 Forbidden Error.

This error is thrown for the URL. If I try to access this URL from the browser also, the same error is thrown. Is there something to help me out.

Thank you.

Hi,

403 Forbidden error means you don't have access to specific URL. (Suppose you are trying to access some DB through this URL,if you don't have access to DB, you will get 403). So, Please check with respective team and then try as above.

Hi Swapna,

Thanks for the suggestion. I will check with the concerned team.

Thanks and Regards,
Guru