how to include attributes in soap xml structure to create a client (Magento 1)

I am trying to create a client using the path "/ api / soap /? Wsdl"
I am sending this structure:

   

  
  
    
      125310091e72358b74d81ef6dasdasadf
      customer.create
      ababab001@a.com

      
        
            
                email
                my_email@hotmail.com
            
        
        
            email
            my_email@hotmail.com
        
      my_email@hotmail.com
      
      
        
          email
          my_email@hotmail.com
        
        my_email@hotmail.com
      
      
        
          email
          my_email@hotmail.com
        
        my_email@hotmail.com
      
      
        
          email
          my_email@hotmail.com
        
        my_email@hotmail.com
      
    
  

connections and everything is fine, however I am getting this answer:

Customer email required

I can't figure out how to send the client attributes (email, username, etc.), I am trying to use arguments, customerData etc., but you are not receiving the email, so what is the correct structure?
(I'm doing it this way, I don't want php methods please, I'm just asking for the correct xml structure to include the customer data in the xml)

Get custom attribute of a client in API Soap magento 1

I need to get custom attributes created for magento 1.9 Soap API v2 clients. From the following code below, I get the "base" data of the clients:

$proxy = new SoapClient('http://mymagento.com/api/v2_soap/?wsdl');
$sessionId = $proxy->login('user', '****');
$result = $proxy->customerCustomerInfo($sessionId, 2);

With that, I take the data as customer_id,email,firstname,lastnameetc.
But in this case, I created client attributes like perfil, category, ativo_pedidos, etc. and I need to get this data to be able to list and also edit the data through the API.

I did a lot of research and so far I have found nothing that can help me. Thanks in advance!

Update SharePoint Online items with SOAP / XML API from outside SharePoint

We need to update (CRUD) the items in the SharePoint Online list from a stand-alone application outside SharePoint of an external company.

This application uses Soap / XML calls to call SP.

The (external) application has been able to connect and update a local SharePoint 2010 list without problems, but we are now migrating to SharePoint Online.

External application can connect and view list items but always throws an error when we try update an item in the list in SharePoint Online

Here is the soap request body (written) and the answer:


   
   
      
         XXXXXX GUID
         
            
   
      1002
      1
      RL101150
      2020-03-03
      andras boros
      
      This is Box 20/1
   
   
      1003
      1
      RL101151
      2020-03-03
      andras boros
      
      This is Box 20/2
   
   
      1004
      1
      RL101152
      2020-03-03
      andras boros
      
      This is Box20/3
   

         
      
   

4:02

   
      
         
            
               
                  0x81020026
                  The list that is referenced here no longer exists.
                  
               
               {TL:DR}
             
            
        
    

Is it possible to update the elements of the SharePoint Online list from a separate web application in a completely different doamin?

And how would we do to handle authentication?

Any help on this would be greatly appreciated.

soap – SAT query web services, XML rejection with incorrect format

I am using SoapUI to test the web service

But it is returning the error Rejection: XML with incorrect format, but I could not identify the wrong person who had this problem.

The following documentation and xml that I am sending is provided:
https://portal.fazenda.sp.gov.br/servicos/sat/Downloads/Manual%20para%20Consultar%20lotes%20enviados%20via%20Webservice%20(Estadual)%20v1%201.pdf


 
   
     35
     0.07
   
 
 
   
     000003021010120200000003001202000440037c091ba-1190-44ee-8e1d-d5808fc65caf
   
 



How to authenticate with the new SharePoint using SOAP?

I would like to authenticate using XML SOAP. I found this resource that seems to be the default for authentication with SharePoint, which is apparently 7 years old and the scheme http://schemas.microsoft.com/sharepoint/soap/ seems to no longer exist. I also receive an error soap:ServerServer was unable to process request. ---> Request format is invalid: Missing required soap:Body element.

My request:




  
    
      
        
          
            
            
          
        
      
      
        
          
            
          
        
      
      
        
          
          
          
        
      
      
        
          
          
          
        
      
      
        
      
      
        
          
            
          
        
      
      
        
          
          
          
          
        
      
    
  
  
    
  
  
    
  
  
    
  
  
    
  
  
    
      
      
    
    
      
      
    
  
  
    
    
      
      
        
      
      
        
      
    
    
      
      
        
      
      
        
      
    
  
  
    
    
      
      
        
      
      
        
      
    
    
      
      
        
      
      
        
      
    
  
   
    
      
    
    
      
    
  


xml: error when consuming SOAP PostMan

I am consuming a SOAP to check issued SAT

Follow the Manual link: https://portal.fazenda.sp.gov.br/servicos/sat/Downloads/Manual%20para%20Consult%20lotes%20enviados%20via%20Webservice%20(Estadual)%20v1%201.pdf

I am using Postman to test before going to PHP, but I have a return error that I cannot solve and even with the manual that seems to me not very clear, I do not understand why the error.



    
        
            soap:Client
            Server did not recognize the value of HTTP Header SOAPAction: CfeConsultarLotes.
            
        
    

This is the error returned

insert image description here

insert image description here

insert image description here

design patterns: how can I decouple my container API from its underlying SOAP implementation?

In our current architecture, a user has multiple ways in which he can change an address (as an example). They can do it through an online portal, through our central processor directly or through a series of applications that communicate with the central processor. I want to design a solution that has a place for all those users to channel, and a place for business logic, instead of half a dozen. I am writing a container API (RESTful) that abstracts the SOAP API from our core processor for ease of use. The reason for the abstraction is because we use a primitive proprietary programming language that does not generate XML as easily as you can simply call a URL.

I am evaluating third-party proxy layers like Mulesoft for this, but I am also investigating solutions that allow business logic to be placed in the RESTful API before I call the core processor. We also want to plan the possibility of the central processor eventually changing, and the SOAP API could be replaced by something else. What design pattern (if any) would you use to decouple the API interface of the underlying SOAP API and the core processor so that if we need to change the backup API to a completely different API that provides similar data and maybe use a mechanism different transport, the external API would not have to change?

I think it would be the adapter pattern or the bridge pattern, but I don't have much experience in SOLID or design patterns and I'm not sure which one would apply (if applicable). I know that the bridge pattern is for an initial design, while the adapter pattern is later. They seem to me both.

Or is it just a control investment at work?

8 – How can I generate custom XML for a SOAP client?

Solved by using cUrl but, I want to use the current form of Drupal:

$headers = array(
                        "POST: the-post-url,
                        "Content-type: text/xml;charset=utf-8",
                        "Accept-Encoding: gzip,deflate",
                        "Cache-Control: no-cache",
                        "Pragma: no-cache",
                        "Host: the-host",
                        "Connection: Keep-Alive"
                    ); //SOAPAction: your op URL

            $url = $soapUrl;

            // PHP cURL  for https connection with auth
            $ch = curl_init();
            curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 1);
            curl_setopt($ch, CURLOPT_URL, $url);
            curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
            //curl_setopt($ch, CURLOPT_USERPWD, $soapUser.":".$soapPassword); // username and password - declared at the top of the doc
            curl_setopt($ch, CURLOPT_HTTPAUTH, CURLAUTH_ANY);
            curl_setopt($ch, CURLOPT_TIMEOUT, 10);
            curl_setopt($ch, CURLOPT_POST, true);
            curl_setopt($ch, CURLOPT_POSTFIELDS, $xmlString); // the SOAP request
            curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);

If there is a better method, let me know!

How to address job posting data for SharePoint 2013 custom timer in the SIEBEL SOAP service failed on the Intranet after enabling TLS 1.2

The custom timer job is implemented in the SharePoint 2013 server farm (local).

The solution is written using .NET Framework 4.5.

Timer jobs run at the Windows service level, so it is not supposed to have anything to do with IIS.

The job sends the SharePoint list items to the SIEBEL SOAP service.

It worked fine until the boys on the network enabled TLS 1.2 through the network.

The URL can be accessed from the browser with SSL.

We haven't updated the WSDL and Proxy class assuming that WSDL doesn't have to do anything with the TLS, correct me if I'm wrong.

We have tried the following from the link

  1. The three fragments of Sebastian Castaldi.
  2. Add Remy Code
  3. Manuel Roldan Code

Also, this somehow helps to change the behavior but it didn't work.
We do not have access to the server, what we can do is provide the WSP solution to the administrator who generates the registry and uses the ones we are receiving under the errors

While trying

System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Ssl3;

Log in

01/14/2020 10:27:04 AM

Error using Ssl3
Exception: the underlying connection was closed: an unexpected error occurred in a reception.

While trying

System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls;

01/14/2020 10:27:04 AM

Error using Tls
Exception: the underlying connection was closed: an unexpected error occurred in a reception.

While trying

System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls11;

Log in

01/14/2020 10:27:04 AM

Error using Tls11
Exception: the underlying connection was closed: an unexpected error occurred in a reception.

While trying

System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;

Log in

01/14/2020 10:27:04 AM

Error using Tls12
Exception: the underlying connection was closed: a trust relationship could not be established for the SSL / TLS secure channel.

We can see that when the Tls12 is used, the Error changes.

I think we have tried everything at the Application / Code level now we need to verify at the server level if we lost something, please let me know.

We can send the data by deleting the following registry value:

HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control SecurityProviders SCHANNEL KeyExchangeAlgorithms PKCS

By deleting the PKCS record, we can PUBLISH the data in SIELBEL

In addition, anyone can share any thoughts that cause this error.

AWS Lambda + SOAP + Self Signed Certs

I want to implement a client for a SOAP application that requires a series of digital certificates to access the API.

I plan to develop it in Java with JAX-RS since it facilitates the implementation of the function in AWS, (As I have read).
But I'm not sure if I can validate the certificates from the lambda, since I also read that API Gateway is not compatible with SOAP.
Anyone know what is the best way to do this development.

Thank you.