Integration

Get Involved. Join the Conversation.

Topic

    Fernando Paes
    Error in OIC integration with OECAnswered
    Topic posted July 16, 2019 by Fernando PaesBlue Ribbon: 750+ Points, tagged API, Integration, PaaS, Sales Cloud, SOAP, Web Services 
    35 Views, 2 Comments
    Title:
    Error in OIC integration with OEC
    Summary:
    Currently the following schemes are not supported: oracle/wss_username_token_client_policy
    Content:

    Hello,

    I've created and activated a new OIC integration with the standard OEC adapter, where OEC will call this integration. When I create the web service in OEC I got this error: 

    Currently the following schemes are not supported: oracle/wss_username_token_client_policy

    and it only allows to create the web service with "Call with basic authentication". I go ahead and when I trigger the integration in OEC, I get this error:

    Exception in expression "OpportunityVO" object function pushOpportunityToOIC() :
    oracle.binding.expr.ServiceInvocationException Unexpected exception caught:
    javax.xml.ws.WebServiceException, msg=javax.xml.soap.SOAPException: Message send failed: Missing WWW-Authenticate header.:
    javax.xml.soap.SOAPException: Message send failed:
    Missing WWW-Authenticate header.: javax.xml.soap.SOAPException: Message send failed: Missing WWW-Authenticate header.
    at "OpportunityVO" object function pushOpportunityToOIC() line 24
    at "oracle.apps.sales.opptyMgmt.opportunities.model.entity.OpportunityEO" trigger "pushOpportunity_BU" line 1
     
    Error 
    Message send failed: Missing WWW-Authenticate header.

     

    Is there any sort of security set up that I need to add in OIC or IDCS so the security is properly set up?

     

    Also, I managed to trick OEC to workaround the error when creating the web service: I removed the Service option, so all the Security Scheme are available, I select "Call with separate user credentials over SSL", then select the Service again and Save and Close. With this set up, I can trigger the integration properly, get no errors, and the OIC integration is properly executed.

    Is it maybe just a bug in OEC?

    Just want to make sure that my OEC-OIC communication is secure.

     

    Thanks in advance

     

    Image:
    Document:

    Best Comment

    Hemanth Lakkaraju

    This is a known issue with OIC-OEC communication and is being handled in future versions from OIC side since OEC cannot handle this.

    Good to know, a new trick/workaround, that works for you. There are other ways to make this work using Groovy Script call or Use another integration with SOAP Adapter as trigger with basic authentication and invoke OEC endpoint from this flow.

    Comment

     

    • Hemanth Lakkaraju

      This is a known issue with OIC-OEC communication and is being handled in future versions from OIC side since OEC cannot handle this.

      Good to know, a new trick/workaround, that works for you. There are other ways to make this work using Groovy Script call or Use another integration with SOAP Adapter as trigger with basic authentication and invoke OEC endpoint from this flow.

    • Fernando Paes

      Hi Hemanth,

      thanks for your answer.

      Just for my knowledge, what would be the workaround using groovy?

      Kind regards