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: Error while decoding access group



When invoking Pega URL via HP load runner tool for load tests, getting exception

Error Messages

2016-02-09 02:11:05,329 [ WebContainer : 1] [TABTHREAD0] [ ] (ernal.authorization.ContextMap) ERROR- Error while decoding access group ({id_1})javax.crypto.IllegalBlockSizeException: Input length (with padding) not multiple of 8 bytes at Source)

Steps to Reproduce

Performance Testing

Root Cause

A third-party product issue. The access group hash of the current session for a given requestor is included in every PRPC URL after login, for example:
Before being placed into the URL, the current access group for the session's PRThread is first encrypted and then HTTP encoded. An asterisk ('*') marks the end of the access group. When the engine receives a request, it will attempt to decrypt the access group hash to get the original name. If the name was not encrypted, exception will be thrown. The encryption puts a mapping between the access group name and it's hash (encryption), and when the decryption is invoked it fails to find the mapping hence the failure. All or part of the test script sending URLs with access group hash that the server doesn't recognize.


Here’s the explanation for the reported behavior: Modify HP load runner test scripts to make sure URLs generated does not have corrupted hash group in them

Published February 29, 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