Web API 401

Hi Richard  by any chance did you try invoking this web API in appian using integration object? Just to make sure that this service is in a good state of being consumed by the end user.

If you are able to call this service using Appian then I recommend to check the following configuration for this API

1. Security privileges for API , specially to that user whose credential is being used in SOAP UI to invoke this service.

2. Authentication mode as Basic Auth with pre-emptive as true which you already have configured.

Concluding this, I believe if you are able to consume this service using Appian integration object, then there might be something wrong with security settings or system firewall which might stop the incoming request. But most probably it should be security issue. But I don't think, weblogic configuration might be causing this

We've validated the user credentials and security privileges for the API but still are not getting anywhere.

If we use Postman and pass along valid cookies, we get the result we wish , but any attempt to do basic Authentication fails no matter what credentials we use.

That's really strange. Are you on Local installation Premise or the Cloud premises?

Because if you are on local premises then i believe you should disable/delete the following

<cookie-config>
<http-only>true</http-only>
<secure>true</secure>
</cookie-config>
<tracking-mode>COOKIE</tracking-mode>

at the following location: <REPO_HOME>\ear\suite.ear\web.war\WEB-INF\web.xml

 

Also if you are on local premises, the i assume, you must have configured

 

conf.suite.SCHEME=http into <REPO_HOME>\ear\suite.ear\conf\custom.properties.<ENVIRONMENT> file.

followed by, restart the server.

But if you are on cloud premises, i believe you need to raise a support ticket to Appian Support to either Restart the Server (So that you can Test this once again when server is re-started) or to fix this issue.

I hope you might get some solution for this problem statement

Alok:

Thanks, we are on-premise, and I'll arrange to have both of these items checked this morning.

Cheers

R

Please do let me know if this worked.

Cheers!

Apologies for the delay, our system administrator found a number of our site-specific configuration items were incorrectly configured. I'll try to dig for the details so that I can post them here!

Thanks Richard for your quick response.