This content has been marked as final. Show 3 replies
Thanks for confirming this. (in the post: [Adding custom information in HTTP Header in an outgoing request from GWWS|https://forums.oracle.com/forums/thread.jspa?threadID=2366358&tstart=0] )
It clarifies the doubts that I was having while reading through the documentation Xu pointed to.
Yes, we need to add HTTP Headers (not SOAP header).
For now we just need to add Basic Authentication HTTP Header for outbound service calls.
We have developed a plugin to do that for now.
And even if the salt plugin takes care of adding the Basic Authentication in the HTTP Header for outgoing calls, I guess we do not have any option to include some custom information in the HTTP Header which might be required in the future.
At-least, not unless we request that enhancement.
Bringing the plugin into our mix requires a lot of changes to our architecture including inclusion of AUTHSVR in the UBB,
Which, in turn, makes it imperative to change the endpoint clients of our application.
In addition to that, the incoming web service calls also need to include TUXEDO authentication information, which would again require either communicating the authentication information to the consumers of our service or device some kind of a proxy which would add the authentication information for all the incoming requests!
With these facts in mind, we were wondering if we have an easier way to include the HTTP header information.
As you say, Maurice, it seems it is not possible yet.
Thank you again for your replies.
Thank you so much for your reply Xu,
Where in our support account would we find the patch to download?
When we try to search under Patches and Fixes
we get the following:
No Sun Change Request (CR) found by the number '8601536'.
No Patch name or number found for '8601536'.
Where would we find the documentation of this BUG fix?
(that is: What do we need to do to meet the desired requirement?)
Thanks and Regards,
Edited by: user1912100 on Apr 24, 2012 12:27 PM