Hi,

We're facing some difficulties on one of our test environments, which hasn't been utilised in a while, when attempting to connect to an external system. We have a Connect REST set up and it uses an Authentication Profile for authenticating.

When we try and connect, we get back a 401 error code and according to the external system's developers, they don't see any sign of our message and inform us that this error code is a sign that the authentication has failed. We've checked the authentication profile and double checked that the endpoint URL matches as well as the client secret and client identifier and they seem to be set up correctly. 

Firstly is there anywhere else I should be checking? Are there any specific checks or rules I should look at?

We've tried this across two of our applications and get the same result when attempting to connect. When I've tried just now and traced it, I can see it's seemingly pulling in the wrong environment settings; as if it's using the wrong production level for our application settings. When I check the System rule, I can see the following notice:

Production level is overridden, the value here will not be applied. Production level source:

JVM Command Line Argument

I'm at a loss about where to check this JVM Command Line Argument - it's not something I've ever configured before. Where would I find this as it'd be easier to adjust this rather than need to go and adjust all our application settings?

Any assistance would be appreciated.

Thanks,

Daniel Jefferies