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

IllegalBlockSizeException thrown trying to login after upgrade

SA-5319

Summary



Errors occurred when the application was updated from Pega 7.1.6 to Pega 7.1.7.

Error Messages



[1/12/15 20:29:20:908 EST] 00000095 SystemOut     O 2015-01-12 20:29:20,906 [    WebContainer : 1] [  STANDARD] [                    ] [                    ] (ernal.authorization.ContextMap) ERROR <HOST>|<IP Address>  - Error while decoding access group (PRSecServlet/8ocUd_nMQ30_O4DyweUtkg[[*)
javax.crypto.IllegalBlockSizeException: Input length (with padding) not multiple of 8 bytes
        at com.ibm.crypto.provider.DESCipher.a(Unknown Source)
        at com.ibm.crypto.provider.DESCipher.engineDoFinal(Unknown Source)


Steps to Reproduce



Log in through Siteminder authentication screen with subsequent URL redirect to PRCustomServlet.

Root Cause



A defect or misconfiguration in the PRPC operating environment:
The SSO login worked in Pega 7.1.6, but the same setup with Siteminder SSO results in the error in Pega 7.1.7. PRCustomServlet was assumed to be configured the same way in both environments, but web.xml of the deployed-PRPC EAR revealed that it did not have the necessary Servlet definition information for PRCustom authentication servlet.


Resolution



Perform the following local-change:
Modify web.xml of the deployed PRPC archive and update it with the necessary information for PRCustom form of Authentication.

Published October 18, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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