Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Faijas Neelikkandi (FaijasNK)
Standard Chartered
Senior Technical Lead
Standard Chartered
MY
FaijasNK Member since 2012 17 posts
Standard Chartered
Posted: Jun 26, 2023
Last activity: Aug 7, 2023
Posted: 26 Jun 2023 3:57 EDT
Last activity: 7 Aug 2023 10:32 EDT
Closed

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 ?

 

***Edited by Moderator Marije to add Capability tags***
To see attachments, please log in.
Pega Platform 8.8.2
Data Integration
Updates
Experience Designer

Posted: 2 years ago
Updated: 2 years ago
Posted: 26 Jun 2023 5:49 EDT
Updated: 26 Jun 2023 6:00 EDT
Marije Schillern (MarijeSchillern)
MOD
Senior Knowledge Management Specialist
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:

Show More

@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:

here, here here. and here.

Show Less
To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice