Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Mashup: Post upgrade to 7.2.1 user sees PRPC Login Screen

SA-31487

Summary



User is upgrading application from PRPC 6.2 version to Pega 7.2.1.

The existing portal code uses PRGateway but user is tying to use the new Mashup code and eliminate the PRGateway.  

When running the gadget  users are getting the Pega login screen. 

Error Messages



Not Applicable


Steps to Reproduce



Not Applicable


Root Cause



After upgrading the Data-Admin-AuthService needed to be reset to use External Authentication because the client is using WebSeal for SSO. 
 

Resolution


 

After an upgrade the Data-Admin-AuthService IACAuthentication gets updated as part of the upgrade process and resets the authentication type to "Use Credentials Stored in PegaRULES" :

This needs to be changed to Use externally stored credentials:



Note:  This change requires a system restart.


Important Note on PRPC Password:

When using Mashups one should never configure the application to send PRPC a base64 encoded password in a production environment.

This "Use Credentials Stored in PegaRULES" is initially set this way for testing and also for gadget creation with the usage of PRGateway.

Since PRGateway is not longer supported starting in Pega 7.2.1 check whether the default vaule set to "Use externally stored credentials".
Suggest Edit

Published December 21, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us