UCMDB Support Tip: lw-sso cryto error pad block corrupted

In the event one gets the following entries in the bsf_security log file:

 

--------------------------------

 

Caused by: com.hp.sw.bto.ast.security.lwcrypto.LWCryptoException: Unable to finalize decryption for the following 208 bytes: [ -31, -104, -74, 117, -127, -81, 45, -6, 65, -117, -104, -59, -7, 81, 62, -1, -104, -5, -4, -85, 67, -89, 23, 15, -65, 36, 12, 10, -62, 28, -93, 82, -22, 88, -31, -127, -83, -85, 81, 39, -115, 115, 13, 62, -92, -76, -4, 79, 74, 27, -7, -117, -17, -24, -46, 112, 48, 22, 71, -13, -6, 106, -111, 54, 42, 49, 110, -61, 95, -124, 87, 86, 48, 27, -75, -19, -2, -108, -35, -74, -116, 105, -90, -73, 125, -92, -27, 25, 4, -26, 44, -13, -18, 6, 59, -35, -57, -26, 104, 8, 66, -97, -96, -56, -42, -39, -119, -76, -18, -14, 48, -17, 72, -102, 105, -114, 65, -87, 31, -94, -84, -105, 59, 85, -126, 36, -49, 79, 27, 126, -23, 53, -20, 45, -63, 65, -126, -12, 32, -71, -7, 42, -47, 66, 69, 52, 94, -88, 105, -6, -47, 64, 118, -116, 44, 47, -30, 62, 97, 38, 45, -64, -127, 26, 110, 72, 127, 80, -38, -4, 33, 118, 32, -58, -122, 64, 2, -54, -2, 113, -1, -93, 91, -58, -115, -115, -48, 81, -122, -54, 11, -114, 55, 95, -97, -128, 79, -19, -67, -101, -56, 99, 111, 74, -50, 65, 52, 31,  ], 192 bytes were already precessed. Current configuration is: com.hp.sw.bto.ast.security.lwcrypto.LWBlockCrypto[ cipher: AES/CBC,  Encoding mode:  Base64Url,  forEncryption: false,  keysize: 256]

  at com.hp.sw.bto.ast.security.lwcrypto.LWBlockCrypto.decrypt(LWBlockCrypto.java:118)

  at com.hp.sw.bto.ast.security.lwcrypto.LWBlockCryptoBase.decrypt(LWBlockCryptoBase.java:168)

  ... 46 more

Caused by: org.bouncycastle.crypto.InvalidCipherTextException: pad block corrupted

  at org.bouncycastle.crypto.paddings.PKCS7Padding.padCount(Unknown Source)

  at org.bouncycastle.crypto.paddings.PaddedBufferedBlockCipher.doFinal(Unknown Source)

  at com.hp.sw.bto.ast.security.lwcrypto.LWBlockCrypto.decrypt(LWBlockCrypto.java:114)

 

 -----------------------

 

Please note this is caused due to an end-user logging in 2 different UCMDB application from the same internet explorer using different tabs.

In order to solve such discrepancy one is required to logging in to both from different internet explorer sessions instead of different tabs.