RTC is not able to authenticate JTS.
When I enters into RTC and try to login JTS, login-page prompts asking for credentials. When I do vice-versa it works fine.
Why RTC is not authenticating JTS
RTC 3.0.0.1
Error-
[11/12/12 14:15:30:914 GMT] 0000000e LTPACrypto < getIVS Exit
[11/12/12 14:15:30:914 GMT] 0000000e LTPACrypto 3 IllegalBlockSizeException probably due to the wrong token factory.
javax.crypto.BadPaddingException: Given final block not properly padded
at java.lang.Throwable.<init>(Throwable.java:67)
at com.ibm.crypto.provider.AESCipher.engineDoFinal(Unknown Source)
at com.ibm.crypto.provider.AESCipher.engineDoFinal(Unknown Source)
at javax.crypto.Cipher.doFinal(Unknown Source)
at com.ibm.ws.security.ltpa.LTPACrypto.decrypt(LTPACrypto.java:2828)
at com.ibm.ws.security.ltpa.LTPAToken2.decrypt(LTPAToken2.java:231)
at com.ibm.ws.security.ltpa.LTPAToken2.<init>(LTPAToken2.java:84)
at com.ibm.ws.security.ltpa.LTPAToken2Factory.validateTokenBytes(LTPAToken2Factory.java:91)
at com.ibm.ws.security.ltpa.LTPAServerObject.validateToken(LTPAServerObject.java:1208)
at com.ibm.ws.security.ltpa.LTPAServerObject.validateToken(LTPAServerObject.java:1111)
at com.ibm.ws.security.ltpa.LTPAServerObject.validateToken(LTPAServerObject.java:1079)
at com.ibm.ws.security.token.WSCredentialTokenMapper.validateLTPAToken(WSCredentialTokenMapper.java:1403)
at com.ibm.ws.hamanager.runtime.DefaultTokenProvider.authenticateMember(DefaultTokenProvider.java:214)
at com.ibm.ws.hamanager.coordinator.dcs.MemberAuthenticatorImpl.authenticateMember(MemberAuthenticatorImpl.java:87)
at com.ibm.ws.dcs.vri.transportAdapter.rmmImpl.ptpDiscovery.DiscoveryRcv.acceptStream(DiscoveryRcv.java:185)
at com.ibm.rmm.ptl.tchan.receiver.PacketProcessor.fetchStream(PacketProcessor.java:470)
at com.ibm.rmm.ptl.tchan.receiver.PacketProcessor.run(PacketProcessor.java:860)
[11/12/12 14:15:30:914 GMT] 0000000e LTPACrypto 3 Total decryption time: 0
[11/12/12 14:15:30:914 GMT] 0000000e ContextManage > getInstance Entry
[11/12/12 14:15:30:915 GMT] 0000000e LTPAServerObj 3 Calling tokenFactory[0].validateTokenBytes() -> com.ibm.ws.security.ltpa.LTPATokenFactory
[11/12/12 14:15:30:915 GMT] 0000000e LTPATokenFact > validateTokenBytes Entry
[11/12/12 14:15:30:915 GMT] 0000000e LTPAToken > LTPAToken(byte[],byte[],LTPAPrivateKey,LTPAPublicKey Entry
[11/12/12 14:15:30:915 GMT] 0000000e LTPAToken 3 Token bytes length = 320
[11/12/12 14:15:30:915 GMT] 0000000e LTPAToken > decrypt Entry
[11/12/12 14:15:30:915 GMT] 0000000e LTPACrypto 3 Cipher used to decrypt: DESede/ECB/PKCS5Padding
[11/12/12 14:15:30:915 GMT] 0000000e LTPACrypto 3 key size: 24
[11/12/12 14:15:30:915 GMT] 0000000e LTPACrypto 3 Array was not properly paded
[11/12/12 14:15:30:915 GMT] 0000000e ContextManage > getInstance Entry
[11/12/12 14:15:30:915 GMT] 0000000e LTPAServerObj 3 Calling tokenFactory[2].validateTokenBytes() -> com.ibm.ws.security.ltpa.AuthzPropTokenFactory
[11/12/12 14:15:30:915 GMT] 0000000e AuthzPropToke > AuthzPropToken from byte[] Entry
[11/12/12 14:15:30:915 GMT] 0000000e AuthzPropToke 3 Before parsing, length: 212
, string: ???8????????XX??'?????D?i?H????E?$????!~@7?5q,???@1nn??J?d??S???(Z>/?')??`?#?B?}?Jf???z???>???d>?}?G??mr-?PBI@??q?s?0?;??(N???V???)?OP??%?@?OJz??Lc?l?SE'???n?ZY???3cU?9l???O?????[!DS4m}??e
[11/12/12 14:15:30:915 GMT] 0000000e AuthzPropToke 3 UserData delimiter not found.
[11/12/12 14:15:30:915 GMT] 0000000e LTPAServerObj < validateToken -> FAILED for primary.737815546 Exit
[11/12/12 14:15:30:915 GMT] 0000000e LTPAServerObj > validateToken(byte[],List,boolean,boolean)737815546 Entry
[B@5cd95cd9
tokenFactoryList=[com.ibm.ws.security.ltpa.LTPATokenFactory@4ccc4ccc, com.ibm.ws.security.ltpa.LTPAToken2Factory@72597259, com.ibm.ws.security.ltpa.AuthzPropTokenFactory@7dea7dea]
primary=false
refreshIfExpired=false
|
One answer
Ralph Schoon (63.5k●3●36●46)
| answered Nov 12 '12, 10:45 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I assume this did not happen from now of then. What is the history? Did you change the configuration. It seems to be related to the SSO setup of WAS:
[11/12/12 14:15:30:914 GMT] 0000000e LTPACrypto 3 Total decryption time: 0 There could be an issue with the LPTA tokens that are used. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.