OBIEE 11g (OID) The Security Token cannot be authenticated (Doc ID 1186513.1)

Last updated on JANUARY 23, 2017

Applies to:

Business Intelligence Suite Enterprise Edition - Version 11.1.1.3.0 [1905] and later
Information in this document applies to any platform.
***Checked for relevance on 06-Aug-2012***

Symptoms

OBIEE 11g was successfully installed.

The application and functionality (Answers, Agent and Alerts, BI Publisher, Oracle Busienss Indicator etc) and it all seemed to work as expected within WebLogic.


The issue arises when WebLogic is set up to use OID (Oracle Internet Direcotry) as opposed to the Embedded LDAP.

The instructions provided on

http://download.oracle.com/docs/cd/E14571_01/bi.1111/e10543/privileges.htm#BABCDCFE

were followed.

A new user called BISystemUser and assigned it to the group called Administrators in OID had been created.

The BISystemUser was assigned to the BISystem Application Role under Fusion Middleware Control.

"Web service authentication failed"
"FailedAuthentication : The security token cannot be authenticated."

Error in receiving the request: oracle.wsm.security.SecurityException: WSM-00
008 : Web service authentication failed..>
<Aug 23, 2010 9:50:40 PM BST> <Error> <oracle.wsm.resources.enforcement> <WSM-07
607> <Failure in execution of assertion {http://schemas.oracle.com/ws/2006/01/se
curitypolicy}wss-username-token executor class oracle.wsm.security.policy.scenar
io.executor.WssUsernameTokenScenarioExecutor.>
<Aug 23, 2010 9:50:40 PM BST> <Error> <oracle.wsm.resources.enforcement> <WSM-07
602> <Failure in WS-Policy Execution due to exception.>
<Aug 23, 2010 9:50:40 PM BST> <Error> <oracle.wsm.resources.enforcement> <WSM-07
501> <Failure in Oracle WSM Agent processRequest, category=security, function=ag
ent.function.service, application=bimiddleware#11.1.1, composite=null, modelObj=
SecurityService, policy=oracle/wss_username_token_service_policy, policyVersion=
null, assertionName={http://schemas.oracle.com/ws/2006/01/securitypolicy}wss-use
rname-token.>
<Aug 23, 2010 9:50:40 PM BST> <Error> <oracle.wsm.agent.handler.wls.WSMAgentHook
> <BEA-000000> <WSMAgentHook: An Exception is thrown: FailedAuthentication : The
security token cannot be authenticated.>
<Aug 23, 2010 10:20:19 PM BST> <Error> <oracle.wsm.resources.security> <WSM-0000
8> <Web service authentication failed.>
<Aug 23, 2010 10:20:19 PM BST> <Error> <oracle.wsm.resources.security> <WSM-0000
6> <Error in receiving the request: oracle.wsm.security.SecurityException: WSM-0
0008 : Web service authentication failed..>
<Aug 23, 2010 10:20:19 PM BST> <Error> <oracle.wsm.resources.enforcement> <WSM-0
7607> <Failure in execution of assertion {http://schemas.oracle.com/ws/2006/01/s
ecuritypolicy}wss-username-token executor class oracle.wsm.security.policy.scena
rio.executor.WssUsernameTokenScenarioExecutor.>
<Aug 23, 2010 10:20:19 PM BST> <Error> <oracle.wsm.resources.enforcement> <WSM-0
7602> <Failure in WS-Policy Execution due to exception.>



"Unsupported OID in the AlgorithmId object"

<Aug 23, 2010 9:46:22 PM BST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=cn removed,OU=organisation name removed,O
=company name removed,C=DE". The loading of the trusted certificat
e list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms