Issue with Rest connectors after upgrade
We have upgraded from pega 7.2.2 to 8.8.2 version .
What we have observed is the Rest connectors that were working earlier in pega 7 is not working now in pega 8 version - Getting 502 exception
Even when we try to configure it new , We are getting 403 exception .
.We are on jboss server .Validated the server settings
There is no change in any server/jboss parameters compared with pega 7 version. Is there any config change required for this ?
Updated: 26 Jun 2023 6:00 EDT
Pegasystems Inc.
GB
@FaijasNK did you check the Known Issues and Resolved Issues documentation?
There are some details under section 'Transport Layer Security (TLS) documentation updated to clarify additional steps after update'
- Cause
- In Pega Platform version 8.7.2 or higher, Rest Connect causes this issue when the lowest allowable SSL/TLS version is set to TLS version 1.0.
- Workaround
- Edit your rule form for outbound connections to use the appropriate protocol supported by your Pega application's underlying Java version, preferably TLS 1.2 if the server supports that version.
Also see Understanding HTTP status codes for troubleshooting common issues
Without enabling SSL/TLS at the application server level, you shouldn't select "Use TLS/SSL" on the service package rule.
Disable "Require TLS/SSL for REST services in this package" on the service package.
Is TEST connectivity on your REST is working correctly?
Next set Debug on REST connector and check that DNS provider does not have existing issues with sending data to one of the IPs.
Check out other forum questions:
@FaijasNK did you check the Known Issues and Resolved Issues documentation?
There are some details under section 'Transport Layer Security (TLS) documentation updated to clarify additional steps after update'
- Cause
- In Pega Platform version 8.7.2 or higher, Rest Connect causes this issue when the lowest allowable SSL/TLS version is set to TLS version 1.0.
- Workaround
- Edit your rule form for outbound connections to use the appropriate protocol supported by your Pega application's underlying Java version, preferably TLS 1.2 if the server supports that version.
Also see Understanding HTTP status codes for troubleshooting common issues
Without enabling SSL/TLS at the application server level, you shouldn't select "Use TLS/SSL" on the service package rule.
Disable "Require TLS/SSL for REST services in this package" on the service package.
Is TEST connectivity on your REST is working correctly?
Next set Debug on REST connector and check that DNS provider does not have existing issues with sending data to one of the IPs.
Check out other forum questions: