(2 votes, average: 5.00 out of 5)
Loading ...Here is an article by Babu Rajendra Prasad Mungara a reader of Siebel Unleashed describing basic details of implementing a Secure Outbound Web Service is Siebel. Though it does not provide implementation steps in detail but it outlines the steps that you need to perform to accomplish that.
- Consume the WSDL File provided by External System
- This will create an Integration Object or multiple Integration Objects and a Proxy Business Service
- Compile these Objects into SRF
- This Proxy Business Service can be invoked through Workflow Process
For this Proxy Business Service, additionally we need to provide the below mentioned additional parameters to build a Siebel WebServices Security Headers in SOAP Header
| Input Argument | Type | Value | Property name |
| getUserInfo_Request:processGetUserInfoInput | Process Property | SiebelMessage | |
| Username | Literal | Test1 | |
| Password | Literal | Test1 |
P.S: Before Simulating the Workflow, Create a Section called EAISubsys under client CFG File
[EAISubsys]
EnableServiceArgTracing = TRUE
- After Simulating the Workflow Process (Proxy Business Service including username and Password), go to TOOLS\Log Directory
- You can observe *.dmp files under TOOLS\Log Directory
- Under this a File Called Outbounddispatcher-output_args.dmp file will be created, this is the file which consists of Siebel WebServices Security Headers as mentioned below
-----------------------------------------------------For more details, connect to Support Web and query as “Implementing WS Security [ID 520484.1]”
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Header>
<wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext">
<wsse:UsernameToken>
<wsse:Username>Test1</wsse:Username>
<wsse:Password>Test1</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body/>
</SOAP-ENV:Envelope>
-----------------------------------------------------------------
Do share your feedback and suggestion. << Previous in series
Authors bio is coming up shortly.
Loading ...
babu, this is awesome. I was waiting for this for a very long time. One more thing I noticed is that, even though these credentials are updated in the WSDLS, we will not be able to see this. Try to use the WSDL given by the external system in SOAP Ui, . In the properties window you can see that the username and passowrd are copied and in the first run itself you will get the soap response. If the same WSDLs is moved to Siebel Tools, you will be getting an authentication error from the target middleware/system. Your suggestion is the solution for this problem. Meanwhile most of the middleware systems have a capability to limit the IP addresses from which the request is coming.In a small organisation, people are using network security rather than web service security. Middleware can also do an anonymous registration based on IP addressess. I dont have an example to figure this right here.