Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies reply
    1
  • Answers answer
    1
  • Subscribers subscribers
    19
  • Views views
    68
  • Users 0 members are here
Related
Options

Integration Studio - PKIX Path Error for generic REST rules using SMAX endpoint

Avi M

Hi everyone,

After upgrading from SMAX 24.1 to 24.4, we encountered an issue with Integration Studio. We have scenarios using a SMAX endpoint connected to the same tenant, mapped to both a SMAX connector and a Generic connector.

Since the upgrade, Generic REST request rules that previously worked now fail with the following error:

{"code":-1,"originalCode":401,"error":"org.springframework.web.client.ResourceAccessException: I/O error on POST request for \"https://<FQDN>/auth/authentication-endpoint/authenticate/token\": PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target","headers":null,"result":null,"originalResponse":null}

The SMAX connector rules are working fine, and the certificate configured in the endpoint is up-to-date. This issue seems specific to Generic REST rules.

Has anyone experienced this or have suggestions to resolve it?

Thank you.

  • Suggested Answer

    0  

    Hi Avi,

    I'm not aware anything has changed from the Integration Studio side for how the Generic connector works, When you upgraded SMAX if the certificates got updated in order to go from 24.1 to 24.4 then this would have an effect on the integration. If the correct root CA certificate has been placed within the configuration of the Generic Connector then the connector should work. If there is a mismatch within the SMAX configuration and what is held in the Integration Engine it might be worth trying to restart the Integration studio pod and seeing if the Connector works after that.

    Another test to try is if you setup a new Connector as Generic does that work just in case something has got screwed up.

    The error message is certainly complaining about the Certificate, so I'd certainly double check the Generic connector certificate configuration just to be 100% sure that isn't causing you the issue. For example do you have an intermediate CA as well as the Root CA that needs to be used?

    Thanks,

    Dave    

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.