Search This Blog

SBL-DAT-00111, SBL-SVC-00281, SBL-UIF-00299, SBL-OSD-02006

Applies to:

Product Release: V7 (Enterprise)
Version: [18379]
Database: Oracle
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 2.8

This document was previously published as Siebel SR 38-3413239318.


SBL-DAT-00111, SBL-SVC-00281, SBL-UIF-00299, SBL-OSD-02006


After applying Siebel Fix Pack, the application crashes whenever a user retrieves a Payment record with Credit Card information.
We also tried to create a new Credit Card Payment record, and the application is crashing.
Credit Card number is encrypted in our application.



Message 1

For the benefit of other readers:

Customer applied Fix Pack on top of Siebel Version, and immediately started experiencing crashes whenever using encrypted data.
This stops happening after rolling back the Fix Pack.
The Call Stack they are getting is the following:


This customer is using AES as the encryption type, with encryption level (key length or strength) of 256 bit.
The same behavior was reproduced in-house on an internal test environment.
We could locate a known Product Defect which has been recently reported in our Knowledge Base:

    - Change Request # 12-1J1ZOUE: After upgrading to SIA, AES 256 encryption causes object manager to crash.

[CONT 1/2...]

Message 2

[... CONT 2/2]

This behavior had been reported by CR # 12-1J1ZOUE on Siebel Version
We logged Fix Request # 12-1KIOH3E requesting for a Quick Fix to be released on top of Fix Pack.
Quickfix [18379] QF0821 is being released by Siebel Engineering to address this issue.

Thank you,

No comments:

Post a Comment