| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SOAP request, via proxy server |
« View previous topic :: View next topic » |
| Author |
Message
|
| sealpup |
 Posted: Tue Sep 21, 2010 4:02 am Post subject: SOAP request, via proxy server |
 |
|
Apprentice
Joined: 21 Sep 2010
Posts: 26
|
Hello,
I am going to risk vilification, public humiliation and abuse in the desperate quest for some help.
There are a few posts on this subject but nothing which has helped resolve my issue.
I'm simply getting a 'HTTP/1.1 407 Proxy Authentication Required' when attempting to access an outside website via our proxy server.
Simple message flow - input>compute>soap request
I have coded
| Code: |
DECLARE CRLF CHAR CAST(X'0D0A' AS CHAR CCSID 1208);
SET OutputLocalEnvironment.Destination.HTTP.ProxyConnectHeaders =
'Proxy-Authorization: Basic Zm5lcmJsZTpwYXNzd29yZA==' || CRLF ||
'Proxy-Connection: Keep-Alive' || CRLF; |
in my compute node. But the SOAP request just doesn't seem to recognise the login information. Or so it appears. I have debugged the flow, and the headers look OK.
Trace as follows.
Also got the security guys to put a trace on the HTTP request. It's tagged on the end, but doesn't add much.
So, erm, help, please. I have been round the houses on this. Clearly, otherwise I wouldn't be risking the public humiliation.
Thanks,
Kevin.
| Code: |
2010-09-21 10:49:59.011024 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''DECLARE ns19 NAMESPACE 'urn:fault.partner.soap.sforce.com';'' at ('.ns19', '1.1').
2010-09-21 10:49:59.011062 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''DECLARE ns2 NAMESPACE 'urn:partner.soap.sforce.com';'' at ('.ns2', '1.1').
2010-09-21 10:49:59.011089 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''DECLARE xmlns NAMESPACE 'http://www.infocomp.com/cbis/common/1.0';'' at ('.xmlns', '1.1').
2010-09-21 10:49:59.011108 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''DECLARE ns NAMESPACE 'http://www.infocomp.com/cbis/uk/request/1.0';'' at ('.ns', '1.1').
2010-09-21 10:49:59.011127 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''DECLARE soapenv NAMESPACE 'http://schemas.xmlsoap.org/soap/envelope/';'' at ('.soapenv', '1.1').
2010-09-21 10:49:59.011146 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''DECLARE encodingStyle NAMESPACE 'http://schemas.xmlsoap.org/soap/';'' at ('.encodingStyle', '1.1').
2010-09-21 10:49:59.011180 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''BEGIN ... END;'' at ('.Salesforce_Compute.Main', '2.2').
2010-09-21 10:49:59.011199 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''SET OutputRoot.SOAP.Body.ns2:login.ns2:username = InputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.ns2:login.ns2:username;'' at ('.Salesforce_Compute.Main', '9.3').
2010-09-21 10:49:59.011329 7904 UserTrace BIP2539I: Node 'Salesforce.Compute': Evaluating expression ''InputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.ns2:login.ns2:username'' at ('.Salesforce_Compute.Main', '9.53'). This resolved to ''InputRoot.XMLNSC.http://schemas.xmlsoap.org/soap/envelope/:Envelope.http://schemas.xmlsoap.org/soap/envelope/:Body.urn:partner.soap.sforce.com:login.urn:partner.soap.sforce.com:username''. The result was ''ROW... Root Element Type=50331648 NameSpace='urn:partner.soap.sforce.com' Name='username' Value='kevin.mayo@aegon.co.uk'''.
2010-09-21 10:49:59.011405 7904 UserTrace BIP2568I: Node 'Salesforce.Compute': Copying sub-tree from ''InputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.ns2:login.ns2:username'' to ''OutputRoot.SOAP.Body.ns2:login.ns2:username''.
2010-09-21 10:49:59.011428 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''SET OutputRoot.SOAP.Body.ns2:login.ns2:password = InputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.ns2:login.ns2:password;'' at ('.Salesforce_Compute.Main', '10.3').
2010-09-21 10:49:59.011466 7904 UserTrace BIP2539I: Node 'Salesforce.Compute': Evaluating expression ''InputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.ns2:login.ns2:password'' at ('.Salesforce_Compute.Main', '10.53'). This resolved to ''InputRoot.XMLNSC.http://schemas.xmlsoap.org/soap/envelope/:Envelope.http://schemas.xmlsoap.org/soap/envelope/:Body.urn:partner.soap.sforce.com:login.urn:partner.soap.sforce.com:password''. The result was ''ROW... Root Element Type=50331648 NameSpace='urn:partner.soap.sforce.com' Name='password' Value='debussy1'''.
2010-09-21 10:49:59.011486 7904 UserTrace BIP2568I: Node 'Salesforce.Compute': Copying sub-tree from ''InputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.ns2:login.ns2:password'' to ''OutputRoot.SOAP.Body.ns2:login.ns2:password''.
2010-09-21 10:49:59.011505 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''SET OutputRoot.SOAP.Header = InputRoot.SOAP.Header;'' at ('.Salesforce_Compute.Main', '13.3').
2010-09-21 10:49:59.011528 7904 UserTrace BIP2543I: Node 'Salesforce.Compute': ('.Salesforce_Compute.Main', '13.32') : Failed to navigate to path element number '2' because it does not exist.
2010-09-21 10:49:59.011543 7904 UserTrace BIP2539I: Node 'Salesforce.Compute': Evaluating expression ''InputRoot.SOAP.Header'' at ('.Salesforce_Compute.Main', '13.32'). This resolved to ''InputRoot.SOAP.Header''. The result was ''EMPTY ROW''.
2010-09-21 10:49:59.011558 7904 UserTrace BIP2567I: Node 'Salesforce.Compute': Assigning NULL to ''OutputRoot.SOAP.Header'', thus deleting it.
2010-09-21 10:49:59.011573 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''DECLARE CRLF CHARACTER CAST(X'0d0a' AS CHARACTER CCSID 1208);'' at ('.Salesforce_Compute.Main', '15.9').
2010-09-21 10:49:59.011604 7904 UserTrace BIP2539I: Node 'Salesforce.Compute': Evaluating expression ''CAST(X'0d0a' AS CHARACTER CCSID 1208)'' at ('.Salesforce_Compute.Main', '15.27'). This resolved to ''CAST(X'0d0a' AS CHARACTER CCSID 1208 )''. The result was '''
'''.
2010-09-21 10:49:59.011623 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''SET OutputLocalEnvironment.Destination.HTTP.ProxyConnectHeaders = 'Proxy-Authorization: Basic aXN0c2ttbzpEZWJ1c3N5Nw==' || CRLF || 'Proxy-Connection: Keep-Alive' || CRLF;'' at ('.Salesforce_Compute.Main', '16.9').
2010-09-21 10:49:59.011646 7904 UserTrace BIP2539I: Node 'Salesforce.Compute': Evaluating expression ''CRLF'' at ('.Salesforce_Compute.Main', '18.66'). This resolved to ''CRLF''. The result was '''
'''.
2010-09-21 10:49:59.011665 7904 UserTrace BIP2539I: Node 'Salesforce.Compute': Evaluating expression '''Proxy-Authorization: Basic aXN0c2ttbzpEZWJ1c3N5Nw==' || CRLF'' at ('.Salesforce_Compute.Main', '18.63'). This resolved to '''Proxy-Authorization: Basic aXN0c2ttbzpEZWJ1c3N5Nw==' || '
'''. The result was '''Proxy-Authorization: Basic aXN0c2ttbzpEZWJ1c3N5Nw==
'''.
2010-09-21 10:49:59.011684 7904 UserTrace BIP2539I: Node 'Salesforce.Compute': Evaluating expression '''Proxy-Authorization: Basic aXN0c2ttbzpEZWJ1c3N5Nw==' || CRLF || 'Proxy-Connection: Keep-Alive''' at ('.Salesforce_Compute.Main', '18.71'). This resolved to '''Proxy-Authorization: Basic aXN0c2ttbzpEZWJ1c3N5Nw==
' || 'Proxy-Connection: Keep-Alive'''. The result was '''Proxy-Authorization: Basic aXN0c2ttbzpEZWJ1c3N5Nw==
Proxy-Connection: Keep-Alive'''.
2010-09-21 10:49:59.011699 7904 UserTrace BIP2539I: Node 'Salesforce.Compute': Evaluating expression ''CRLF'' at ('.Salesforce_Compute.Main', '18.108'). This resolved to ''CRLF''. The result was '''
'''.
2010-09-21 10:49:59.011711 7904 UserTrace BIP2539I: Node 'Salesforce.Compute': Evaluating expression '''Proxy-Authorization: Basic aXN0c2ttbzpEZWJ1c3N5Nw==' || CRLF || 'Proxy-Connection: Keep-Alive' || CRLF'' at ('.Salesforce_Compute.Main', '18.105'). This resolved to '''Proxy-Authorization: Basic aXN0c2ttbzpEZWJ1c3N5Nw==
Proxy-Connection: Keep-Alive' || '
'''. The result was '''Proxy-Authorization: Basic aXN0c2ttbzpEZWJ1c3N5Nw==
Proxy-Connection: Keep-Alive
'''.
2010-09-21 10:49:59.011734 7904 UserTrace BIP2566I: Node 'Salesforce.Compute': Assigning value ''Proxy-Authorization: Basic aXN0c2ttbzpEZWJ1c3N5Nw==
Proxy-Conne... (data of len 83 truncated)'' to field / variable ''OutputLocalEnvironment.Destination.HTTP.ProxyConnectHeaders''.
2010-09-21 10:49:59.011756 7904 UserTrace BIP2537I: Node 'Salesforce.Compute': Executing statement ''RETURN TRUE;'' at ('.Salesforce_Compute.Main', '26.3').
2010-09-21 10:49:59.011795 7904 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'Salesforce.Compute'.
2010-09-21 10:49:59.011863 7904 UserTrace BIP2539I: Node 'Salesforce.Trace': Evaluating expression ''Root'' at ('', '1.3'). This resolved to ''Root''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2010-09-21 10:49:59.012073 7904 UserTrace BIP4067I: Message propagated to output terminal for trace node 'Salesforce.Trace'.
The trace node 'Salesforce.Trace' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2010-09-21 10:49:59.012390 7904 UserTrace BIP3615I: SOAP message written with '0' MTOM elements.
2010-09-21 10:49:59.012485 7904 UserTrace BIP3719I: Node 'Salesforce.login to salesforce' sending SOAP request via transport 'HTTP' ('test.salesforce.com:443') for operation 'login' of type 'request-response'.
See subsequent messages for success or failure messages relating to this request, and for any transport-specific messages.
No action required.
2010-09-21 10:49:59.015064 7904 UserTrace BIP3633I: Node 'Salesforce.login to salesforce' sending HTTP data to URL 'test.salesforce.com:443' at host 'test.salesforce.com' (port 8080).
The broker is sending data via HTTP to a remote server at host 'test.salesforce.com' (port 8080) using URL 'test.salesforce.com:443'. See subsequent messages for success or failure messages relating to this request.
No action required.
2010-09-21 10:49:59.074153 7904 UserTrace BIP3634I: Node 'Salesforce.login to salesforce' received HTTP data from host 'test.salesforce.com' with status code of 407.
The broker has received data via HTTP from a remote server at host 'test.salesforce.com' with an HTTP status code of 407. Status codes beginning with a 2 indicate success; others imply errors in either client or server.
No action required.
2010-09-21 10:49:59.074432 7904 UserTrace BIP2231E: Error detected whilst processing a message in node 'Salesforce.login to salesforce'.
The message broker detected an error whilst processing a message in node 'Salesforce.login to salesforce'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2010-09-21 10:49:59.074615 7904 RecoverableException BIP3162S: An HTTP error occurred. The HTTP Request-Line was: ''CONNECT test.salesforce.com:443 HTTP/1.1
''.
The HTTP Request Header bitstream (if any) to be used was: 'X'486f73743a20746573742e73616c6573666f7263652e636f6d3a3434
330d0a50726f78792d436f6e6e656374696f6e3a206b6565702d616c69
76650d0a0d0a''. The HTTP Request Message Body bitstream (if any) to be used was: ''''. The HTTP Reply Header bitstream (if any) received from the server was: 'X'485454502f312e31203430372050726f78792041757468656e74696
36174696f6e2052657175697265640d0a50726f78792d41757468656e
7469636174653a204e544c4d0d0a50726f78792d41757468656e74696
36174653a204241534943207265616c6d3d226165675f61645f726561
6c6d220d0a43616368652d436f6e74726f6c3a206e6f2d63616368650d0
a507261676d613a206e6f2d63616368650d0a436f6e74656e742d54797
0653a20746578742f68746d6c3b20636861727365743d7574662d380d
0a50726f78792d436f6e6e656374696f6e3a20636c6f73650d0a5365742
d436f6f6b69653a20424353492d435330413236463634373d323b2050
6174683d2f0d0a436f6e6e656374696f6e3a20636c6f73650d0a436f6e74
656e742d4c656e6774683a203831300d0a0d0a''. The HTTP Reply Message Body bitstream (if any) received from the server was: 'X'3c48544d4c3e3c484541443e0a3c5449544c453e4163636573732044
656e6965643c2f5449544c453e0a3c2f484541443e0a3c424f44593e0a3
c464f4e5420666163653d2248656c766574696361223e0a3c6269673e
3c7374726f6e673e3c2f7374726f6e673e3c2f6269673e3c42523e0a3c2f
464f4e543e0a3c626c6f636b71756f74653e0a3c5441424c4520626f726
465723d302063656c6c50616464696e673d312077696474683d223830
25223e0a3c54523e3c54443e0a3c464f4e5420666163653d2248656c76
6574696361223e0a3c6269673e4163636573732044656e6965642028
61757468656e7469636174696f6e5f6661696c6564293c2f6269673e0a
3c42523e0a3c42523e0a3c2f464f4e543e0a3c2f54443e3c2f54523e0a3c
54523e3c54443e0a3c464f4e5420666163653d2248656c76657469636
1223e0a596f75722063726564656e7469616c7320636f756c64206e6f7
42062652061757468656e746963617465643a202243726564656e746
9616c732072657175697265642e222e20596f752077696c6c206e6f742
06265207065726d69747465642061636365737320756e74696c20796f
75722063726564656e7469616c732063616e20626520766572696669
65642e0a3c2f464f4e543e0a3c2f54443e3c2f54523e0a3c54523e3c5444
3e0a3c464f4e5420666163653d2248656c766574696361223e0a54686
973206973207479706963616c6c792063617573656420627920616e2
0696e636f727265637420757365726e616d6520616e642f6f722070617
373776f72642c2062757420636f756c6420616c736f206265206361757
36564206279206e6574776f726b2070726f626c656d732e0a3c2f464f4e
543e0a3c2f54443e3c2f54523e0a3c54523e3c54443e0a3c464f4e54206
66163653d2248656c766574696361222053495a453d323e0a3c42523e
0a466f7220617373697374616e63652c20636f6e7461637420796f7572
206e6574776f726b20737570706f7274207465616d2e0a3c2f464f4e543
e0a3c2f54443e3c2f54523e0a3c2f5441424c453e0a3c2f626c6f636b717
56f74653e0a3c2f464f4e543e0a3c2f424f44593e3c2f48544d4c3e0a''. Ensure that the HTTP data is valid.
See the following messages for information pertaining to this error.
2010-09-21 10:49:59.074638 7904 RecoverableException BIP3691S: A SOAP Request node encountered an HTTP error whilst making an HTTP Request. The HTTP Request was made to the destination ''https://test.salesforce.com/services/Soap/u/19.0''. The HTTP Status-Line returned was: ''HTTP/1.1 407 Proxy Authentication Required''.
An error occurred whilst performing an HTTP Request. Check that the remote server is responding and that the request is specified correctly.
See the following messages for information pertaining to this error.
2010-09-21 10:49:59.074745 7904 UserTrace BIP2539I: Node 'Salesforce.Trace1': Evaluating expression ''Root'' at ('', '1.3'). This resolved to ''Root''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2010-09-21 10:49:59.074928 7904 UserTrace BIP4067I: Message propagated to output terminal for trace node 'Salesforce.Trace1'.
The trace node 'Salesforce.Trace1' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2010-09-21 10:49:59.075008 7904 UserTrace BIP2537I: Node 'Salesforce.Compute2': Executing statement ''DECLARE ns19 NAMESPACE 'urn:fault.partner.soap.sforce.com';'' at ('.ns19', '1.1').
2010-09-21 10:49:59.075031 7904 UserTrace BIP2537I: Node 'Salesforce.Compute2': Executing statement ''DECLARE ns2 NAMESPACE 'urn:partner.soap.sforce.com';'' at ('.ns2', '1.1').
2010-09-21 10:49:59.075050 7904 UserTrace BIP2537I: Node 'Salesforce.Compute2': Executing statement ''DECLARE xmlns NAMESPACE 'http://www.infocomp.com/cbis/common/1.0';'' at ('.xmlns', '1.1').
2010-09-21 10:49:59.075073 7904 UserTrace BIP2537I: Node 'Salesforce.Compute2': Executing statement ''DECLARE ns NAMESPACE 'http://www.infocomp.com/cbis/uk/request/1.0';'' at ('.ns', '1.1').
2010-09-21 10:49:59.075462 7904 UserTrace BIP2537I: Node 'Salesforce.Compute2': Executing statement ''DECLARE soapenv NAMESPACE 'http://schemas.xmlsoap.org/soap/envelope/';'' at ('.soapenv', '1.1').
2010-09-21 10:49:59.075481 7904 UserTrace BIP2537I: Node 'Salesforce.Compute2': Executing statement ''DECLARE encodingStyle NAMESPACE 'http://schemas.xmlsoap.org/soap/';'' at ('.encodingStyle', '1.1').
2010-09-21 10:49:59.075515 7904 UserTrace BIP2537I: Node 'Salesforce.Compute2': Executing statement ''BEGIN ... END;'' at ('.Salesforce_Compute2.Main', '2.2').
2010-09-21 10:49:59.075534 7904 UserTrace BIP2537I: Node 'Salesforce.Compute2': Executing statement ''SET OutputRoot.SOAP.Body.ns19:LoginFault.ns19:exceptionCode = OutputRoot.SOAP.Body.ns19:LoginFault.ns19:exceptionCode;'' at ('.Salesforce_Compute2.Main', '10.3').
2010-09-21 10:49:59.075557 7904 UserTrace BIP2543I: Node 'Salesforce.Compute2': ('.Salesforce_Compute2.Main', '10.65') : Failed to navigate to path element number '2' because it does not exist.
2010-09-21 10:49:59.075588 7904 UserTrace BIP2539I: Node 'Salesforce.Compute2': Evaluating expression ''OutputRoot.SOAP.Body.ns19:LoginFault.ns19:exceptionCode'' at ('.Salesforce_Compute2.Main', '10.65'). This resolved to ''OutputRoot.SOAP.Body.urn:fault.partner.soap.sforce.com:LoginFault.urn:fault.partner.soap.sforce.com:exceptionCode''. The result was ''EMPTY ROW''.
2010-09-21 10:49:59.075790 7904 UserTrace BIP2567I: Node 'Salesforce.Compute2': Assigning NULL to ''OutputRoot.SOAP.Body.ns19:LoginFault.ns19:exceptionCode'', thus deleting it.
2010-09-21 10:49:59.075817 7904 UserTrace BIP2537I: Node 'Salesforce.Compute2': Executing statement ''SET OutputRoot.XMLNSC.ns19:LoginFault.ns19:exceptionMessage = OutputRoot.SOAP.Body.ns19:LoginFault.ns19:exceptionMessage;'' at ('.Salesforce_Compute2.Main', '11.3').
2010-09-21 10:49:59.075839 7904 UserTrace BIP2543I: Node 'Salesforce.Compute2': ('.Salesforce_Compute2.Main', '11.65') : Failed to navigate to path element number '5' because it does not exist.
2010-09-21 10:49:59.075859 7904 UserTrace BIP2539I: Node 'Salesforce.Compute2': Evaluating expression ''OutputRoot.SOAP.Body.ns19:LoginFault.ns19:exceptionMessage'' at ('.Salesforce_Compute2.Main', '11.65'). This resolved to ''OutputRoot.SOAP.Body.urn:fault.partner.soap.sforce.com:LoginFault.urn:fault.partner.soap.sforce.com:exceptionMessage''. The result was ''EMPTY ROW''.
2010-09-21 10:49:59.075885 7904 UserTrace BIP2567I: Node 'Salesforce.Compute2': Assigning NULL to ''OutputRoot.XMLNSC.ns19:LoginFault.ns19:exceptionMessage'', thus deleting it.
2010-09-21 10:49:59.075931 7904 UserTrace BIP2537I: Node 'Salesforce.Compute2': Executing statement ''RETURN TRUE;'' at ('.Salesforce_Compute2.Main', '17.3').
2010-09-21 10:49:59.075981 7904 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'Salesforce.Compute2'.
2010-09-21 10:49:59.076484 7904 UserTrace BIP2638I: The MQ output node 'Salesforce.HUB.REQUEST.AWD.SALESFORCE.FAILURE' attempted to write a message to queue ''HUB.REQUEST.AWD.SALESFORCE.FAILURE'' connected to queue manager ''''. The MQCC was '0' and the MQRC was '0'.
2010-09-21 10:49:59.076503 7904 UserTrace BIP2622I: Message successfully output by output node 'Salesforce.HUB.REQUEST.AWD.SALESFORCE.FAILURE' to queue ''HUB.REQUEST.AWD.SALESFORCE.FAILURE'' on queue manager ''''.
2010-09-21 10:51:15.413903 4748 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2010-09-21 10:51:15.413995 4748 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2010-09-21 10:51:15.414019 4748 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2010-09-21 10:51:15.414067 4748 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '243' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
Threads encountered in this trace:
2256 2368 2660 2904 3184 3468 3880 3904 3968 4008 4116 4188 4192 4268 4356 4496 4512 4580 4616 4704 4740 4748 4828 4936 4960 5056 5456 5720 5884 6004 6076 6628 6944 7356 740 7500 7628 7808 7820 7904 836
start transaction -------------------
CPL Evaluation Trace: transaction ID=618190700
<Proxy>
MATCH: authenticate(aeg_ad_realm) authenticate.force(no) authenticate.mode(auto)
<ssl>
MATCH: server.certificate.validate(no)
<Proxy>
<Cache>
MATCH: request.icap_service(new_outbound_group)
<Cache>
<Proxy>
MATCH: client.address=10.33.40.61 trace.request(yes) trace.rules(yes)
connection: client.address=10.33.40.61 proxy.port=8080
time: 2010-09-21 09:49:54 UTC
CONNECT tcp://test.salesforce.com:443/
DNS lookup was unrestricted
user: unauthenticated
EXCEPTION(authentication_failed): Authentication failed either because credentials were not provided or they could not be validated
url.category: Business and Economy@Websense
authentication-required realm=aeg_ad_realm (NTLM and BASIC)
stop transaction -------------------- |
[moderator]added code tags for readability[/moderator] |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Sep 21, 2010 4:07 am Post subject: Re: SOAP request, via proxy server |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sealpup wrote: |
| I am going to risk villification, public humiliation and abuse in the desperate quest for some help. |
Not using code tags to make the trace readable will increase all 3. 
| sealpup wrote: |
| But the SOAP request just doesn't seem to recognise the login information. Or so it appears. I have debugged the flow, and the headers look OK. |
Even this part:
| sealpup wrote: |
| Code: |
Assigning NULL to ''OutputRoot.SOAP.Header'', thus deleting it. |
|
??
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 21, 2010 4:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Use wireshark or something else, perhaps the TCP/IP Monitor in Toolkit if you're running broker locally, to capture the HTTP Request as sent.
It doesn't seem correct at first glance to assign multiple ProxyConnectHeaders as a single string like that, but I've not tried to do this before so I could be wrong.
There might also be something in security profiles that can help here. |
|
| Back to top |
|
|
| sealpup |
| Posted: Tue Sep 21, 2010 4:25 am Post subject: |
|
|
Apprentice
Joined: 21 Sep 2010
Posts: 26
|
Vitor,
Thank you so much for your constructive reply *cough*.
Jeff, thanks.
The ProxyConnectHeaders code I took from the IBM website (and also lifted to this forum). It seems to perform correctly in debug.
I will follow your other suggestions and plough on. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
