wsse:InvalidSecurity Error When Testing FND_PROFILE Web Service in Oracle Applications R 12.1.2 from...

最新推荐文章于 2024-09-14 19:55:29 发布

weixin_33709609

最新推荐文章于 2024-09-14 19:55:29 发布

阅读量308

点赞数

文章标签：数据库 ui

wsse:InvalidSecurity Error When Testing FND_PROFILE Web Service in Oracle Applications R 12.1.2 from SOAP UI (Doc ID 1314946.1)

Modified:

10-Nov-2013

Type:

PROBLEM

In this Document

Symptoms

Cause

Solution

References

Applies to:

Oracle E-Business Suite Integrated SOA Gateway - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Checked for relevance on 08-JUN-2013

Symptoms

On: 12.1.3 version, Installation Issues

When attempting to test the FND_PROFILE web service from SOAP UI,
the following error occurs in SOAP UI:

<faultcode>wsse:InvalidSecurity</faultcode>
<faultstring>Missing <wsse:Security> in SOAP Header</faultstring>

The issue can be reproduced at will with the following steps:
1. Generate the WDSL (successful) in Integrated SOA Gateway
2. Deploy the web service in ISG
3. Create grant to user sysadmin and adadmin in ISG
4. In SOAP UP, copy the WSDL link in and it recognizes the functions that are exposed.
5. Run the project after putting in some parameters for the FND_PROFILE, i.e application language etc.

Cause

Missing wsse security tokens.

The SOAP header didn't have the user name and password to do the authentication so that the web service cannot be called.

Solution

To implement the solution, please execute the following steps:

1. Open project in SOAP UI.

2. Add the following wsse:security section in the SOAP header:

<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" mustUnderstand="1">
<wsse:UsernameToken>
<wsse:Username>asadmin</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">asadmin</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>

3. Save the file and retest the issue.

4. Migrate the solution as appropriate to other environments.

References

NOTE:764149.1 - Missing in SOAP Header when Calling Secured WebService from BPEL Leading to SOAPException
NOTE:954125.1 - AIA 2.4: Product MDM BPEL process QueryItemListPIMProvABCSImpl fails during the call to ItemService

Didn't find what you are looking for?Ask in Community...