I am attempting to do a remote data query in Attendant. I keep running into warnings and errors. Does anyone know if https is supported while doing a remote data query? I just want to clarify. I am going to describe two (2) different scenarios. ***Note - If I paste the https WSDL in the browser of the server, it takes me to a log in screen, if I enter the data that is supplied in attendant in the Enhanced SOAP Request Tool Configuration, it allows log in to that service. If I click on the certificate information of that browser window it is the *.xxxxx.dev certificate. 1. I use the https WSDL - on attendant I fill in the Enhanced SOAP Request Tool Configuration: I add the username, the password, and the Certificate Subject's Common Name. I select or deselect any, all or none of the Ignore SSL options. I get the following error: SOAPHTTPRequestEx_Internal2 : ErrorCode: error.i3openssl.ssl Description: SSL_CTX_use_certificate_chain_file() failed Hostname: CICDEV2 Function: i3openssl::initialize_ssl_context() File(Line): //core/2.1_su06/int/src/i3openssl/ssl_context.cpp#1(410) Parameters: 'file' => "e:\I3\IC\Certificates\SOAP\*.xxxxx.dev" Nested: ErrorCode: error.i3openssl.ssl.0x140dc002 Description: system lib Hostname: CICDEV2 Function: SSL_CTX_use_certificate_chain_file File(Line): /ssl_rsa.c(722) Parameters: 'library' => "SSL routines" Nested: ErrorCode: error.i3openssl.ssl.0x20074002 Description: system lib Hostname: CICDEV2 Function: FILE_CTRL File(Line): /bio/bss_file.c(400) Parameters: 'library' => "BIO routines" Nested: ErrorCode: error.i3openssl.ssl.0x200107b Description: Unknown error Hostname: CICDEV2 Function: fopen File(Line): /bio/bss_file.c(398) Parameters: 'library' => "system library" [Context Attribute 'Thread Name']: IP-Handler [Context Attribute 'IP Context Id']: 11947 2. I use the https WSDL, on attendant I fill in the Enhanced SOAP Request Tool Configuration: I add the username, the password, I leave the Certificate Subject's Common Name blank. I select or deselect any, all or none of the Ignore SSL options. I get the following warning: SOAPHTTPRequestEx_Internal2 : An error occurred during execution: HTTPStatusCode: No viable connection for {@transport} HTTPStatusText: 24572 ResponseHeaders: Unknown [Context Attribute 'Thread Name']: IP-Handler [Context Attribute 'IP Context Id']: 11962 Ang

Do you have a valid certificate? It needs to go in the D:\I3\IC\Certificates\SOAP\ folder. You may have to create the folder.

Originally posted by jgaedke;32556
Do you have a valid certificate? It needs to go in the D:\I3\IC\Certificates\SOAP\ folder. You may have to create the folder.

Yes, I have the folder created and the file in the folder.

When I add the certificate into the attendant field for the client common name the certificate error goes away and I get the following error: SOAPHTTPRequestEx_Internal2 : An error occurred during execution: HTTPStatusCode: No viable connection for {@transport} HTTPStatusText: 24572 ResponseHeaders: Unknown [Context Attribute 'Thread Name']: IP-Handler [Context Attribute 'IP Context Id']: 12191

According to ININ and after hours of trying, I found no way to use https in Attendant. It was much easier just to assign requests to attributes and use a common handler to make the call and assign to another attribute for evaluation.

Originally posted by RobertWC;32559
According to ININ and after hours of trying, I found no way to use https in Attendant. It was much easier just to assign requests to attributes and use a common handler to make the call and assign to another attribute for evaluation.

Thank you so much for trying and sharing your thoughts! I will head in that direction. Ang

Originally posted by RobertWC;32559
According to ININ and after hours of trying, I found no way to use https in Attendant. It was much easier just to assign requests to attributes and use a common handler to make the call and assign to another attribute for evaluation.

I have not really messed with any handlers, can a handler call out to https? The only way I can get this information from our system of record is by going in with https. Ang

Here is a sample handler that does a lookup on a public Cdyne.com web service that does a MOD 10 lookup on a credit card number to verify whether the number is valid and what type of card it is. It does not use https: but it gives you a good look at handler tools and you can modify it for your own site. It is hard-coded to send a card number of 4111111111111111 which should return "true" and "visa". The web service and parameters are designated in the SOAP Create Envelope and SOAP Add RPC Parameter steps. To run it, you can just copy the .ihd to your server, publish it and make it active, then at a command-line on the server run "sendcustomnotification checkcc checkcc" The tool step that sends the call to the web service is: SOAP HTTP Request Ex3 This SOAP tool issues an HTTP request to the specified URL with the SOAP request envelope as payload. The response body is parsed and returned as response envelope. This tool is similar to SOAP HTTP Request but eliminates the need to use semaphores to limit the number of SOAP requests. It also supports SSL secured connections (https). This tool is similar to the SOAP HTTP Request Ex2 tool, except that: This tool does not use MSXML to send SOAP requests. This tool expects the certificate file to be present in a specific directory: $Server/IC/Certificates/SOAP The certificate must be in PEM format. For more information about converting a certificate to the PEM format, see: https://my.inin.com/Support/Pages/KB-Details.aspx?EntryID=Q125241321600149 This tool supports many concurrent requests. This tool does not fully support NTLM. If you absolutely need to use NTLM, you should use the SOAP HTTP Request Ex2 tool instead. This tool does not use Windows Certificate store to check for validity of the certificate, and it uses openssl to do the verification.

Note that the certificate must be in PEM format. I don't know if that is what you are using. This is the same tool step used by Attendant in the latest versions of IC (actually, the Attendant handler does a check for "Old SSL?" to choose between the Ex2 and Ex3 variants of the SOAP HTTP Request EX..." tool).

Originally posted by GGanahl;32563
Note that the certificate must be in PEM format. I don't know if that is what you are using. This is the same tool step used by Attendant in the latest versions of IC (actually, the Attendant handler does a check for "Old SSL?" to choose between the Ex2 and Ex3 variants of the SOAP HTTP Request EX..." tool).

Thank you, and yes, it is in pem format Ang