Oracle WebCenter Announcement service error (failure to authenticate the user)

The Oracle WebCenter  announcement service task flow provides ability to post announcement to all authenticated users.

We have used announcement service in our portal application and recently we hit with below error

"failure to authenticate the user testuser@abc.com, due to: Unexpected error occured,due to:
oracle.j2se.ws.client.jaxws.JSRSOAPFaultException:Client received SOAP Fault from server:SOAP must
understan error.Server could not understand one or more SOAP headers:{http://docs.oasis-open.org
/wss/2004/01/oasis-200401-wss-wsssecurity-1.0.xsd}security"


and here is the work around which we did to address the error.

From oracle document source i found that,this error may be caused due to various reasons. We need to Check the following 

•        Ensure that the OWSM SAML policy setting is appropriately defined between the discussions connection and the discussions server.

•        For the WebCenter Portal Discussions service, review WC_Spaces-diagnostic.log for errors and exceptions. If the log does not provide enough information to correct errors, then turn on debugging for the oracle.webcenter.collab.share and oracle.webcenter.collab.forum packages.

•        For the back-end discussions server, review WC_Collaboration-diagnostics.log and jive.error.log inside your domain's$DOMAIN_HOME/config/fmwconfig/servers/SERVER_NAME/owc_discussions/logs directory. If the logs do not provide enough information to correct errors, then turn on debugging for Oracle WebCenter Portal's Discussion Server. To turn on debug logs, log on to Oracle WebCenter Portal's Discussion Server admin console, go to page logs, the Debug tab, and enable. Restart the WC_Collaboration domain to change the logging setting.

•        Make sure that the WebCenter Portal application and the back-end discussions server are in time sync. This is important with OWSM WS-Security.

 In our case,  I faced this error due to the first reason (Service policy is not attached in the server) and below are the steps

We need to make sure that , client policy attached in JDeveloper discussion connection server should match to the service policy attached in the web logic server.

In the JDeveloper, the policy URI for authenticated access is set as marked below and we need to make sure the corresponding service policy is attached in the server. If there is no service policy attached then it will through the above mentioned error.

Step 1: Go to discussion server in your enterprise manager server, navigate to Application Deployment -> web service  as shown below

Step 2: Click on Authenticated Web service endpoints as shown below.

Step 3: Check whether corresponding service policy attached under OWSM policies as shown below.

Step 4: if there is no policy attached then you need to attach the policy, in this case i am attaching, the corresponding service policy as shown below.

i)             Click on Attach/Detach icon

ii)            Select the service policy and attach

  

iii)           Click on OK and It will ask for restarting of  the application .

Note: Once you restart the application please do check whether your service policy is attached or not. some times,  although service policy is attached and still it throws the same error, then try detaching the policy and attach once again.

Hope this helps !