Siebel Credentials Not Working In BIPublisher And Roles Not Listed With BIP User After Implementing Siebel Security Model
(Doc ID 2978425.1)
Last updated on OCTOBER 04, 2023
Applies to:
Siebel CRM - Version 17.0 [IP2017] and laterInformation in this document applies to any platform.
Symptoms
After enabling the Siebel Security Model the following error was given when connecting with Siebel Credentials:
Similar error was given when connecting with BIP credentials and accessing the "Roles" section.
The following error was found in the bipublisher.log:
[2023-09-26T16:36:04.663+04:00] [bi_server1] [WARNING] [] [oracle.xdo] [tid: 32] [userId: <anonymous>] [ecid: f406cae0-6101-46e8-a0e7-928f2d754f01-00000093,0] [APP: bipublisher] [partition-name: DOMAIN] [tenant-name: GLOBAL] [SI-Key: ssi] oracle.xdo.security.ValidateException: javax.xml.ws.WebServiceException: Could not send Message.[[
Caused by: javax.net.ssl.SSLException: SSLException invoking https://<SiebSrvrhost>:<Portnumber >/eai_enu/start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&WSSOAP=1: readHandshakeRecord
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Caused by: javax.net.ssl.SSLException: readHandshakeRecord
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Enable Siebel Security Model.
2. Configure the webservice URL.
3. Log in with siebel credentials.
Changes
New integration between Siebel and Oracle Analytics Publisher 6.4
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |