Home / user-108565

moneyBox's questions

Martin Hope
moneyBox
Asked: 2022-06-04 18:42:20 +0800 CST
  • 3

I have a couple of instances created in the same VPC. Create an EFS to have a "store" in the pair of instances, likewise when creating the EFS I make sure to be in the same Region as where I create the EC2 Instances and on the same VPC.

Having already created the EFS and opening it with the "Associate" option, I observe the recommendations of the mount command , but when I do it in any of the two EC2 instances it keeps me thinking.... and it never mounts :'(

The Network options of the EFS resource have a security indicated as "sg-cd669dcb (default)", that when looking at it in the Security Groups, I see that the Input and Output ports are 100% open because it says: All Traffic (in both of them).

Anyway, I still can't mount the resource and I've run out of ideas :'(.... What do you recommend?

Update 06/16/2021

To have the AWS EFS better organized, in the security part I have removed the "default" and placed a security group called "nfs", which configures everything open like this:

Security group > nfs enter image description here

despite this I still can't mount it, not even from an EC2 instance, less from my own laptop :(

aws
Martin Hope
moneyBox
Asked: 2020-10-30 14:13:17 +0800 CST
  • 2

I'm having trouble passing arguments to my script in bash. To simplify I made this example that in the same way does not work.

It is supposed that when invoking it as it programa.sh piedrashould give you a message, if it does not match the expected one it gives you an error. But it doesn't work for me, it always says "PAPER":

#!/bin/bash
# programa.sh

if [ "$1"="papel" ]; then
        echo -e ""
        echo -e "Hola invocaste PAPEL"
        echo -e ""
elif [ "$1"="piedra" ]; then
        echo -e ""
        echo -e "Hola invocaste PIEDRA"
        echo -e ""
else
        echo -e "Error: solo se soportan los argumento: papel y piedra"
fi
bash
Martin Hope
moneyBox
Asked: 2020-04-24 13:20:33 +0800 CST
  • -1

I am generating an XML where at the moment of embedding the Certificate it must go in a certain encoding that, despite the fact that I have searched, I have not been able to generate it.

Taking a valid XML as an example, I have noted that the embedded Certificate presents instead of the line break , the encoding:

Therefore, in my XMLs I have tried to place said element with:

$certData= file_get_contents("/ruta/archivo.cer");
wordwrap($certData, 76, "\r\n", true);

But this only gives me the , how can I place: ??

Here Valid XML:

MIIIoTCCBomgAwIBAgIIW6qCaBJlC8wwDQYJKoZIhvcNAQELBQAwgbQxIzAhBgkqhkiG9w0BCQEW FGluZm9AYW5kZXNzY2QuY29tLmNvMSMwIQYDVQQDExpDQSBBTkRFUyBTQ0QgUy5BLiBDbGFzZSBJ

Here MY Invalid Xml (output):

MIIIoTCCBomgAwIBAgIIW6qCaBJlC8wwDQYJKoZIhvcNAQELBQAwgbQxIzAhBgkqhkiG9w0BCQEW FGluZm9AYW5kZXNzY2QuY29tLmNvMSMwIQYDVQQDExpDQSBBTkRFUyBTQ0QgUy5BLiBDbGFzZSBJ

php
Martin Hope
moneyBox
Asked: 2020-04-16 09:18:27 +0800 CST
  • 0

I am sending electronic invoices to the Webservice SOAPTesting (enablement) of the DIANand I get the following error:

com.indra.mmdd.signature.exceptions.ValidateException: xades4j.providers.CannotSelectCertificateException: The available certificate selector didn't match any certificates

I want to think that the problem is in the Digital Test Certificate that I have, but days ago I bought a valid certificate from the ANDES SCD entity (approved by ONAC) and it continues to mention the same error.

Has anyone experienced the same thing and can give me some feedback?

Cheers !

webservice
Martin Hope
moneyBox
Asked: 2020-04-12 13:12:56 +0800 CST
  • -1

I have a Raspberry PI 3 with Raspbian Desktop (debian) and I want Firefox to automatically run when I start the graphical environment.

linux
Martin Hope
moneyBox
Asked: 2020-03-15 08:05:04 +0800 CST
  • 1

I am integrating XADES-EPES digital signature in PHP on the UBL standard, I have read a lot about it and in several repositories they do the signing in different ways, well, what goes inside the DiguestValue and SignatureValue , finally leaving me with the doubt that : information really goes into those elements? .

To verify my progress and arrive at the correct signature, I am relying on this validator https://tools.chilkat.io/xmlDsigVerify.cshtml and I have opened a repository where I share my PHP code as far as I am advanced: https:// gitlab.com/siegroupmx/xmlsinger

I go to the matter....

>> How are DigestValues ​​generated for References within SignedInfo ??

My procedure for this is simply take the Node (for example KeyInfo) canonicalized to C14N and then pass it through an Algorithm (sha1, sha256, etc...), then convert it to Base64 and put the result over DigestValue , my process is it correct ???

Simple and quick example:

Needless to say, in the example below I am skipping the process where I create the Singature tag and its inner elements.

<?php
const XMLDSIGNS= 'http://www.w3.org/2000/09/xmldsig#';

$xmlSigned= 'mixml.xml';
$xml= new DOMDocument();
$xml->preserveWhiteSpace= FALSE;
$xml->formatOutput= true;
$xml->load($xmlSigned);

$xp= new DOMXPath($xml);
$xp->registerNamespace('secdsig', self::XMLDSIGNS);
$keyinfo= $xp->query('.//secdsig:Signature/secdsig:KeyInfo');

$hash= hash("sha256", $keyinfo->item(0)->C14N(), true);
$base64= base64_encode($hash);
echo $base64; # imprime LcOJdpKtT7sgjbblkmGyYrSUslXMlw0TyCc8SOUBJQM=
?>

And in the XML:

<ds:Reference URI="#xmldsig-a837805e-9235-a8bb-7ab4-688282608259-keyinfo">
    <ds:Transforms>
        <ds:Transform Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/>
    </ds:Transforms>
    <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
    <ds:DigestValue>LcOJdpKtT7sgjbblkmGyYrSUslXMlw0TyCc8SOUBJQM=</ds:DigestValue>
</ds:Reference>
....
....
<ds:KeyInfo Id="xmldsig-a837805e-9235-a8bb-7ab4-688282608259-keyinfo">
    ... todas las etiquetas internas....
</ds:KeyInfo>

>> How is the SignatureValue generated???

In my procedure I take the SignedInfo node canonicalized to C14N, sign them with openssl_sign() and convert the result to Base64 and put it inside the SignatureValue. Is this correct what I do ???

Quick example:

<?php
const XMLDSIGNS= 'http://www.w3.org/2000/09/xmldsig#';

$xmlOut= 'mixml.xml';
$xml= new DOMDocument();
$xml->preserveWhiteSpace= FALSE;
$xml->formatOutput= true;
$xml->load($xmlOut);

$xp= new DOMXPath($xml);
$xp->registerNamespace('secdsig', self::XMLDSIGNS);

$si= $xp->query('.//secdsig:Signature/secdsig:SignedInfo'); # signedinfo
openssl_sign($si->item(0)->C14N(), $signature, $this->privateKey, OPENSSL_ALGO_SHA256);
$dato= base64_encode($signature); # esto va en SignatureValue

$sv= $xp->query('.//secdsig:Signature/secdsig:SignatureValue'); # signaturevalue
$sv->item(0)->nodeValue= $dato;
?>

And the SignatureValue inside the XML is:

<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="xmldsig-bfcdf0f0-2655-b952-9c85-77493d9f241f">
    <ds:SignedInfo>
        <ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/>
        <ds:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
        <ds:Reference Id="xmldsig-bfcdf0f0-2655-b952-9c85-77493d9f241f-ref0" URI="">
            <ds:Transforms>
                <ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
            </ds:Transforms>
            <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
            <ds:DigestValue>KWOvQ3tWaygQXkkvfI6s9UO0azjQgc0YGp9JANDXYis=</ds:DigestValue>
        </ds:Reference>
        <ds:Reference URI="#xmldsig-a837805e-9235-a8bb-7ab4-688282608259-keyinfo">
            <ds:Transforms>
                <ds:Transform Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/>
            </ds:Transforms>
            <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
            <ds:DigestValue>LcOJdpKtT7sgjbblkmGyYrSUslXMlw0TyCc8SOUBJQM=</ds:DigestValue>
        </ds:Reference>
    </ds:SignedInfo>
    <ds:SignatureValue Id="xmldsig-bfcdf0f0-2655-b952-9c85-77493d9f241f-sigvalue">
        ZGcaOhKK3Uzp64T11LHFKAy1eOkKeMpvKNNAeBFapJxbyCr8iQDkGQ2B+VQFYLWZnDneK6Cuc6uDtUw14q4mlYoarlIRVvLlsiQK0OmFrdWEM4sd62WPP2N0GpUOOh/I/BjggsqNV1OOWG2xutZNbdh4maJzxEbcLuU8SrdPuU6q38bTAw/QJyQ5F4eiRr++28sR9G3yV0nTzkZXR5QNPScdrbwrMtH/vkBx0FfV8ErzubwKyPdvQSbugmLMk8hd7Rnn5SRg8JaxQhCC5TDPC3KOmj5Nh1zHmzATZaRAbP0XNoYsDLnQtmteo5/RL2NHGvHYbP0teUF43nHXu/KAVg==
    </ds:SignatureValue>

>> CONCLUSION

The validator tells me that the Signature is wrong, and that the signature of the references is also wrong :(

Link to an example https://gitlab.com/siegroupmx/xmlsinger/blob/master/examples/example_out.xml

Certificate: https://gitlab.com/siegroupmx/xmlsinger/blob/master/tmp/certificado.pem

Signature: https://gitlab.com/siegroupmx/xmlsinger/blob/master/tmp/firma.pem

Key: legal_person_evidence

xml
Martin Hope
moneyBox
Asked: 2020-03-05 19:37:37 +0800 CST
  • 2

I am uploading an invoice to the DIAN tax entity in Colombia and at first I had details about missing elements in the XML, after polishing this part now the DIAN Soap webservice returns the following error message:

Parameters [ NIT=ERROR DOCNUMBER=OK ISSUEDATE=OK ]

The Request I generate is...

For obvious reasons I have filled the real NIT with "x", as well as other security elements of the Soap-Header.

I have already verified in detail:

  1. That the Issuer NIT is well written and correct.
  2. That the NIT of the Issuer exists in the DIAN (use that of Legal Entity).
  3. That the Receiver NIT is different from the issuer.
  4. That the Receiver NIT Exists in the DIAN (use the Natural Person).
  5. I am making the requests to the Test WebService (enablement) of the DIAN.
<soapenv:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rep="http://www.dian.gov.co/servicios/facturaelectronica/ReportarFactura">
    <soapenv:header>
        <wsse:security soapenv:mustunderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsse:usernametoken wsu:id="UsernameToken-2">
                <wsse:username>3bxxxxxx-7xxx-4xxx-bxxx-39xxxxxxxxxx</wsse:username>
                <wsse:password type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile1.0#PasswordText">1d97....ae</wsse:password>
                <wsse:nonce encodingtype="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security1.0#Base64Binary">bW...MQ==</wsse:nonce>
                <wsu:created>2019-03-04T22:19:11.000Z</wsu:created>
            </wsse:usernametoken>
        </wsse:security>
    </soapenv:header>
    <soapenv:body>
        <rep:enviofacturaelectronicapeticion>
            <rep:nit>901xxxxxx</rep:nit>
            <rep:invoicenumber>PRUE980000000</rep:invoicenumber>
            <rep:issuedate>2019-03-04T22:19:11</rep:issuedate>
            <rep:document>UEsD....FbXBhcw==</rep:document>
        </rep:enviofacturaelectronicapeticion>
    </soapenv:body>
</soapenv:envelope>
php
Martin Hope
moneyBox
Asked: 2020-02-26 16:10:18 +0800 CST
  • 0

I am generating an Electronic Invoice for the DIAN tax entity in Colombia, but it tells me that I have semantic errors in the invoice, I have already exhausted all the possibilities, I have reviewed the XML and its elements in detail, and I do not see that there is any typo or missing, For now, I can only ask here if someone has had the same thing happen to them:

Error at line (140): cvc-complex-type.2.4.a: Invalid content was found starting with element 'cbc:ProfileExecutionID'. One of '{"urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2":ID}' is expected.

The load is generated towards the test Webservice ( https://facturaelectronica.dian.gov.co/habilitacion/B2BIntegrationEngine/FacturaElectronica/facturaElectronica.wsdl ), I use a Test Certificate and valid test access.

And the XML I send is:

<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="http://www.dian.gov.co/contratos/facturaelectronica/v1" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:clm54217="urn:un:unece:uncefact:codelist:specification:54217:2001" xmlns:clm66411="urn:un:unece:uncefact:codelist:specification:66411:2001" xmlns:clmIANAMIMEMediaType="urn:un:unece:uncefact:codelist:specification:IANAMIMEMediaType:2003" xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2" xmlns:qdt="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2" xmlns:sts="http://www.dian.gov.co/contratos/facturaelectronica/v1/Structures" xmlns:udt="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xades="http://uri.etsi.org/01903/v1.3.2#" xmlns:xades141="http://uri.etsi.org/01903/v1.4.1#" xsi:schemaLocation="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 http://docs.oasis-open.org/ubl/os-UBL-2.1/xsd/maindoc/UBL-Invoice-2.1.xsd">
  <ext:UBLExtensions>
    <ext:UBLExtension>
      <ext:ExtensionContent>
        <sts:DianExtensions>
          <sts:InvoiceControl>
            <sts:InvoiceAuthorization>9000000124786152</sts:InvoiceAuthorization>
            <sts:AuthorizationPeriod>
              <cbc:StartDate>2018-10-29</cbc:StartDate>
              <cbc:EndDate>2020-12-31</cbc:EndDate>
            </sts:AuthorizationPeriod>
            <sts:AuthorizedInvoices>
              <sts:Prefix>PRUE</sts:Prefix>
              <sts:From>980000000</sts:From>
              <sts:To>985000000</sts:To>
            </sts:AuthorizedInvoices>
          </sts:InvoiceControl>
          <sts:InvoiceSource>
            <cbc:IdentificationCode listAgencyID="6" listAgencyName="United Nations Economic Commission for Europe" listSchemeURI="urn:oasis:names:specification:ubl:codelist:gc:CountryIdentificationCode-2.0">CO</cbc:IdentificationCode>
          </sts:InvoiceSource>
          <sts:SoftwareProvider>
            <sts:ProviderID schemeAgencyID="195" schemeAgencyName="CO, DIAN (Dirección de Impuestos y Aduanas Nacionales)">700200857</sts:ProviderID>
            <sts:SoftwareID schemeAgencyID="195" schemeAgencyName="CO, DIAN (Dirección de Impuestos y Aduanas Nacionales)">d80990f3-e5e5-41d0-a632-aa45298ed0da</sts:SoftwareID>
          </sts:SoftwareProvider>
          <sts:SoftwareSecurityCode schemeAgencyID="195" schemeAgencyName="CO, DIAN (Dirección de Impuestos y Aduanas Nacionales)">6d6582ba5cfc2b148cf2b4607b9e4b1966e07a4b4e9c3a707cfe354fb165b74a4f853595a95f8854f4e7731cd75043fa</sts:SoftwareSecurityCode>
        </sts:DianExtensions>
      </ext:ExtensionContent>
    </ext:UBLExtension>
    <ext:UBLExtension>
      <ext:ExtensionContent>
        <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="xmldsig-a3bf7689-a251-8584-2509-54da26046c5f">
          <ds:SignedInfo>
            <ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/>
            <ds:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
            <ds:Reference Id="xmldsig-a3bf7689-a251-8584-2509-54da26046c5f" URI="">
              <ds:Transforms>
                <ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
              </ds:Transforms>
              <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
              <ds:DigestValue>oQsBT4snpzP/xB2zT+iqA6lKMVbUgjd3hcyUJMTdTrA=</ds:DigestValue>
            </ds:Reference>
            <ds:Reference URI="#xmldsig-66507247-d3ff-7227-2e9e-48dd4a3fb534-keyinfo">
              <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
              <ds:DigestValue>ZovwLaIxJg/ezn50L3XtXWLYlTCMeKqBPiydw0kwx+4=</ds:DigestValue>
            </ds:Reference>
            <ds:Reference URI="#xmldsig-79b2dde6-d858-48a9-c825-d7f8d6fad906-object">
              <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
              <ds:DigestValue>ooyWjfK7JWdym+4kOE1JfZt3WYKPhNhTbmU/dq03XQU=</ds:DigestValue>
            </ds:Reference>
          </ds:SignedInfo>
          <ds:SignatureValue Id="xmldsig-a3bf7689-a251-8584-2509-54da26046c5f">RbN1TS7IuG/hB/FMCGONsKkkVioK/5HarZS1bIJj/AHJpXK8bNAN9IIwq+sbG8XpoqiqrqQEdHqwW8T+fap8BIr6WKSEl8h9yK90S112AQQHUDLIV261Gp3iNNRj4+3wYmhpdsdPFFnzzixKa0I0SsuQ25mqM+0HaIIk8Wj6TDC41Wdhu5Q1iWeEsWFEY0+LBhjpFXdZd66qHiq0nd/g6s4ZrRcrcKEsjzrSKe/kQzKI6ya4HXkiwsvZX/mokx+2Oa1/dGQzyVXJhQA1X5Ke66iV2cSdouRiK3v1pamGiwd3MSIvBU66+9Fmr5SNff9g3sHVwM4hnNYrLA0noIIHVw==</ds:SignatureValue>
          <ds:KeyInfo Id="xmldsig-66507247-d3ff-7227-2e9e-48dd4a3fb534-keyinfo">
            <ds:X509Data>
              <ds:X509Certificate>
MIIGvDCCBKSgAwIBAgIUMDAwMDEwMDAwMDA0MTExMDYxODEwDQYJKoZIhvcNAQEL
BQAwggGyMTgwNgYDVQQDDC9BLkMuIGRlbCBTZXJ2aWNpbyBkZSBBZG1pbmlzdHJh
Y2nDs24gVHJpYnV0YXJpYTEvMC0GA1UECgwmU2VydmljaW8gZGUgQWRtaW5pc3Ry
YWNpw7NuIFRyaWJ1dGFyaWExODA2BgNVBAsML0FkbWluaXN0cmFjacOzbiBkZSBT
ZWd1cmlkYWQgZGUgbGEgSW5mb3JtYWNpw7NuMR8wHQYJKoZIhvcNAQkBFhBhY29k
c0BzYXQuZ29iLm14MSYwJAYDVQQJDB1Bdi4gSGlkYWxnbyA3NywgQ29sLiBHdWVy
cmVybzEOMAwGA1UEEQwFMDYzMDAxCzAJBgNVBAYTAk1YMRkwFwYDVQQIDBBEaXN0
cml0byBGZWRlcmFsMRQwEgYDVQQHDAtDdWF1aHTDqW1vYzEVMBMGA1UELRMMU0FU
OTcwNzAxTk4zMV0wWwYJKoZIhvcNAQkCDE5SZXNwb25zYWJsZTogQWRtaW5pc3Ry
YWNpw7NuIENlbnRyYWwgZGUgU2VydmljaW9zIFRyaWJ1dGFyaW9zIGFsIENvbnRy
aWJ1eWVudGUwHhcNMTgwNjA1MjAwNDIzWhcNMjIwNjA1MjAwNTAzWjCCASkxNzA1
BgNVBAMTLlNFUlZJQ0lPUyBERSBJTk5PVkFDSU9OIFBBUkEgRU1QUkVTQVMgU0Eg
REUgQ1YxNzA1BgNVBCkTLlNFUlZJQ0lPUyBERSBJTk5PVkFDSU9OIFBBUkEgRU1Q
UkVTQVMgU0EgREUgQ1YxNzA1BgNVBAoTLlNFUlZJQ0lPUyBERSBJTk5PVkFDSU9O
IFBBUkEgRU1QUkVTQVMgU0EgREUgQ1YxCzAJBgNVBAYTAk1YMSgwJgYJKoZIhvcN
AQkBFhlhbmdlbC5jYW50dUBzaWUtZ3JvdXAubmV0MSUwIwYDVQQtExxTSUUxMTAy
MjFMNjIgLyBDQUpBODQxMjE0UEE5MR4wHAYDVQQFExUgLyBDQUpBODQxMjE0SFRT
TlJOMDAwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCrLyWdoAIVAJpV
yW1ZybuqxNfe7VzlmRej/mAvpmcJ76cNVrtU16/PYz3ZLNTnC0FA7LZe8tpdDVWr
/+kiqHpaBgfVIDrnCnlQ8G9WGla70vb4Yg+T2IQ715Vg9w3idqlluvUIfH8Z2RQD
cNQ5QjGSCyx4qhcChqJBJUiGv1kCGVnphMk2WdX0SX8VfFL75hCvK5xLIlz8v3uu
wmtgZdbTuAfTbjGgmAAWlcMzG5bmtjuB72ZrH3PzbUEUyk3EbXHniRyNXk+L02Mk
qoezsZ+Bw/jvEfFZbK3i4NohWNyhbcrHvVqFPGxzg8uCEzOOAw4VFI63xoErn836
zjlCjX1PAgMBAAGjTzBNMAwGA1UdEwEB/wQCMAAwCwYDVR0PBAQDAgPYMBEGCWCG
SAGG+EIBAQQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwDQYJ
KoZIhvcNAQELBQADggIBAGDdRNgzy4YGJEPDqm1NEaUXI4aZLjT43Ubx5sotqL4g
0Eqy8dVw8i/JI6YTK02qBtTJrR033l0OhW+X/lMQWrLzD2wNIRiY0B2Zf27JXD4H
RiukySwy5N25qJxZ+GndZOEZcnKl1Zl9lva3GvOoYmFYTdgZ3iCItGE6Y2Mnsv4R
NNGhDIUrTAIB8OOEgh879n2nKRPccvBq1lFMIXWImlaD76KsKBl+vTBs9bJ0e5Z3
UJDnIdV76JeAiKvAlP5VE3mpSXQ34GQmr9bzwkPy1BD5IMOWXxapuqypXA6poahY
dsN3cJMlWZ5TlLa/woPoyGpkpHPqQ2RrPE6ZRqUFANN/A8cU/SeLl5kTIYOPo3ii
NBBDKWl48AVacp4xl13wYaPRx/6OCNCwaN4pmxjCu+bcQasqb93j/TeQXxOnCEMY
yqOlrESLH/UklDfHVwhC5PGaP3xRY2aNsI3mwS5/NsYNioP9zn5iJ2lzSB4roQRU
iuHTFRnSTZvmjHL8AcpUSfmAjWH98LtfFydICrXTPsuJ5i1BogXaRI9Kga223QVJ
SCzW1wPqj7UhJJABhlEDVQ0yXi+a/9U2/jBr0uavf/EH7cigbfP+9DCoVucXZXy+
BzXz8mMI6Evp4tYiiBNOoxqV/W3mZKjQJkg6fJUSFOVyfrgRILl42aDadZiH+i15
</ds:X509Certificate>
            </ds:X509Data>
          </ds:KeyInfo>
          <ds:Object Id="xmldsig-79b2dde6-d858-48a9-c825-d7f8d6fad906-object">
            <xades:QualifyingProperties xmlns:xades="http://uri.etsi.org/01903/v1.3.2#" xmlns:xades141="http://uri.etsi.org/01903/v1.4.1#">
              <xades:SignedProperties>
                <xades:SignedSignatureProperties>
                  <xades:SigningTime>2019-02-25T18:16:17-05:00</xades:SigningTime>
                  <xades:SigningCertificate>
                    <xades:Cert>
                      <xades:CertDigest>
                        <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
                        <ds:DigestValue>X02jKw4C5nHlpr4FJE3Wl9KojJQSaoY+Y0QuBwRkjhk=</ds:DigestValue>
                      </xades:CertDigest>
                      <xades:IssuerSerial>
                        <ds:X509IssuerName>C=CO,L=Bogota D.C.,O=Andes SCD.,OU=Division de certificacion entidad final,CN=CA ANDES SCD S.A. Clase II,1.2.840.113549.1.9.1=#1614696e666f40616e6465737363642e636f6d2e636f</ds:X509IssuerName>
                        <ds:X509SerialNumber>9128602840918470673</ds:X509SerialNumber>
                      </xades:IssuerSerial>
                    </xades:Cert>
                  </xades:SigningCertificate>
                  <xades:SignaturePolicyIdentifier>
                    <xades:SignaturePolicyId>
                      <xades:SigPolicyId>
                        <xades:Identifier>https://facturaelectronica.dian.gov.co/politicadefirma/v2/politicadefirmav2.pdf</xades:Identifier>
                        <xades:Description>Política de firma para facturas electrónicas de la República de Colombia</xades:Description>
                      </xades:SigPolicyId>
                      <xades:SigPolicyHash>
                        <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
                        <ds:DigestValue>dMoMvtcG5aIzgYo0tIsSQeVJBDnUnfSOfBpxXrmor0Y=</ds:DigestValue>
                      </xades:SigPolicyHash>
                    </xades:SignaturePolicyId>
                  </xades:SignaturePolicyIdentifier>
                  <xades:SignerRole>
                    <xades:ClaimedRoles>
                      <xades:ClaimedRole>supplier</xades:ClaimedRole>
                    </xades:ClaimedRoles>
                  </xades:SignerRole>
                </xades:SignedSignatureProperties>
              </xades:SignedProperties>
            </xades:QualifyingProperties>
          </ds:Object>
        </ds:Signature>
      </ext:ExtensionContent>
    </ext:UBLExtension>
  </ext:UBLExtensions>
  <cbc:UBLVersionID>UBL 2.1</cbc:UBLVersionID>
  <cbc:CustomizationID>1</cbc:CustomizationID>
  <cbc:ProfileID>DIAN 2.1</cbc:ProfileID>
  <cbc:ProfileExecutionID>2</cbc:ProfileExecutionID>
  <cbc:ID>PRUE980000000</cbc:ID>
  <cbc:UUID schemeID="2" schemeName="SHA-256">bfe8bf2ec657a77e67f541ae82860f03d9beb9f5ae8f87d88b0498e44b7bc697</cbc:UUID>
  <cbc:IssueDate>2019-02-25</cbc:IssueDate>
  <cbc:IssueTime>18:16:17-05:00</cbc:IssueTime>
  <cbc:DueDate>2019-03-27</cbc:DueDate>
  <cbc:InvoiceTypeCode>01</cbc:InvoiceTypeCode>
  <cbc:Note>Factura emitida desde la plataforma https://www.moneybox.com.co</cbc:Note>
  <cbc:TaxPointDate>2019-02-25</cbc:TaxPointDate>
  <cbc:DocumentCurrencyCode>COP</cbc:DocumentCurrencyCode>
  <cbc:LineCountNumeric>1</cbc:LineCountNumeric>
  <cac:OrderReference>
    <cbc:ID>PO12345678</cbc:ID>
  </cac:OrderReference>
  <cac:AccountingSupplierParty>
    <cbc:AdditionalAccountID schemeAgencyID="195">1</cbc:AdditionalAccountID>
    <cac:Party>
      <cac:PartyName>
        <cbc:Name>Moneybox Colombia SAS</cbc:Name>
      </cac:PartyName>
      <cac:PhysicalLocation>
        <cac:Address>
          <cbc:ID>88780</cbc:ID>
          <cbc:CityName>Bogotá</cbc:CityName>
          <cbc:CountrySubentity>Cundinamarca</cbc:CountrySubentity>
          <cac:AddressLine>
            <cbc:Line>20 de noviembre 300</cbc:Line>
          </cac:AddressLine>
          <cac:Country>
            <cbc:IdentificationCode>CO</cbc:IdentificationCode>
          </cac:Country>
        </cac:Address>
      </cac:PhysicalLocation>
      <cac:PartyTaxScheme>
        <cbc:RegistrationName>Moneybox Colombia SAS</cbc:RegistrationName>
        <cbc:CompanyID schemeID="2" schemeName="31" schemeAgencyName="CO, DIAN (Dirección de Impuestos y Aduanas Nacionales)" schemeAgencyID="195">700200857</cbc:CompanyID>
        <cbc:TaxLevelCode listName="05">O-99</cbc:TaxLevelCode>
        <cac:RegistrationAddres>
          <cbc:CityName>Bogotá</cbc:CityName>
          <cbc:CountrySubentity>Colombia</cbc:CountrySubentity>
          <cbc:CountrySubentityCode>CO</cbc:CountrySubentityCode>
          <cac:AddressLine>
            <cbc:Line>20 de noviembre 300</cbc:Line>
          </cac:AddressLine>
          <cac:Country>
            <cbc:IdentificationCode>CO</cbc:IdentificationCode>
            <cbc:Name>Colombia</cbc:Name>
          </cac:Country>
        </cac:RegistrationAddres>
        <cac:TaxScheme>
          <cbc:ID>01</cbc:ID>
          <cbc:Name>IVA</cbc:Name>
        </cac:TaxScheme>
      </cac:PartyTaxScheme>
      <cac:PartyLegalEntity>
        <cbc:RegistrationName>Moneybox Colombia SAS</cbc:RegistrationName>
        <cbc:CompanyID schemeID="2" schemeName="31" schemeAgencyName="CO, DIAN (Dirección de Impuestos y Aduanas Nacionales)" schemeAgencyID="195">700200857</cbc:CompanyID>
      </cac:PartyLegalEntity>
      <cac:Contact>
        <cbc:Telephone>52 899 310 1442</cbc:Telephone>
        <cbc:ElectronicMail>[email protected]</cbc:ElectronicMail>
      </cac:Contact>
    </cac:Party>
  </cac:AccountingSupplierParty>
  <cac:AccountingCustomerParty>
    <cbc:AdditionalAccountID>2</cbc:AdditionalAccountID>
    <cac:Party>
      <cac:PartyName>
        <cbc:Name>Publico en General</cbc:Name>
      </cac:PartyName>
      <cac:PhysicalLocation>
        <cac:Address>
          <cbc:ID>88700</cbc:ID>
          <cbc:CityName>Reynosa</cbc:CityName>
          <cbc:PostalZone>88700</cbc:PostalZone>
          <cac:AddressLine>
            <cbc:Line>20 de noviembre 300</cbc:Line>
          </cac:AddressLine>
          <cac:Country>
            <cbc:IdentificationCode>CO</cbc:IdentificationCode>
            <cbc:Name>Colombia</cbc:Name>
          </cac:Country>
        </cac:Address>
      </cac:PhysicalLocation>
      <cac:PartyTaxScheme>
        <cbc:RegistrationName>Publico en General</cbc:RegistrationName>
        <cbc:CompanyID schemeID="9" schemeName="31" schemeAgencyName="CO, DIAN (Dirección de Impuestos y Aduanas Nacionales)" schemeAgencyID="195">806000509</cbc:CompanyID>
        <cbc:TaxLevelCode listName="04">O-99</cbc:TaxLevelCode>
        <cac:TaxScheme>
          <cbc:ID>01</cbc:ID>
          <cbc:Name>IVA</cbc:Name>
        </cac:TaxScheme>
      </cac:PartyTaxScheme>
      <cac:Person>
        <cbc:FirstName>Publico</cbc:FirstName>
        <cbc:FamilyName>en General</cbc:FamilyName>
      </cac:Person>
      <cac:Contact>
        <cbc:Telephone>8999266046</cbc:Telephone>
        <cbc:ElectronicMail>[email protected]</cbc:ElectronicMail>
      </cac:Contact>
    </cac:Party>
  </cac:AccountingCustomerParty>
  <cac:PaymentMeans>
    <cbc:ID>1</cbc:ID>
    <cbc:PaymentMeansCode>10</cbc:PaymentMeansCode>
  </cac:PaymentMeans>
  <cac:TaxTotal>
    <cbc:TaxAmount currencyID="COP">90000.00</cbc:TaxAmount>
    <cac:TaxSubtotal>
      <cbc:TaxableAmount currencyID="COP">1000000.00</cbc:TaxableAmount>
      <cbc:TaxAmount currencyID="COP">90000.00</cbc:TaxAmount>
      <cac:TaxCategory>
        <cbc:Percent>9.00</cbc:Percent>
        <cac:TaxScheme>
          <cbc:ID>01</cbc:ID>
          <cbc:Name>IVA</cbc:Name>
        </cac:TaxScheme>
      </cac:TaxCategory>
    </cac:TaxSubtotal>
  </cac:TaxTotal>
  <cac:TaxTotal>
    <cbc:TaxAmount currencyID="COP">0.00</cbc:TaxAmount>
    <cac:TaxSubtotal>
      <cbc:TaxableAmount currencyID="COP">0.00</cbc:TaxableAmount>
      <cbc:TaxAmount currencyID="COP">0.00</cbc:TaxAmount>
      <cac:TaxCategory>
        <cbc:Percent>0.00</cbc:Percent>
        <cac:TaxScheme>
          <cbc:ID>02</cbc:ID>
          <cbc:Name>INC</cbc:Name>
        </cac:TaxScheme>
      </cac:TaxCategory>
    </cac:TaxSubtotal>
  </cac:TaxTotal>
  <cac:TaxTotal>
    <cbc:TaxAmount currencyID="COP">0.00</cbc:TaxAmount>
    <cac:TaxSubtotal>
      <cbc:TaxableAmount currencyID="COP">0.00</cbc:TaxableAmount>
      <cbc:TaxAmount currencyID="COP">0.00</cbc:TaxAmount>
      <cac:TaxCategory>
        <cbc:Percent>0.00</cbc:Percent>
        <cac:TaxScheme>
          <cbc:ID>03</cbc:ID>
          <cbc:Name>ICA</cbc:Name>
        </cac:TaxScheme>
      </cac:TaxCategory>
    </cac:TaxSubtotal>
  </cac:TaxTotal>
  <cac:LegalMonetaryTotal>
    <cbc:LineExtensionAmount currencyID="COP">1000000.00</cbc:LineExtensionAmount>
    <cbc:FreeOfChargeIndicator>false</cbc:FreeOfChargeIndicator>
    <cbc:TaxExclusiveAmount currencyID="COP">90000.00</cbc:TaxExclusiveAmount>
    <cbc:ChargeTotalAmount currencyID="COP">1090000.00</cbc:ChargeTotalAmount>
    <cbc:PayableAmount currencyID="COP">1090000.00</cbc:PayableAmount>
  </cac:LegalMonetaryTotal>
  <cac:InvoiceLine>
    <cbc:ID>1</cbc:ID>
    <cbc:InvoicedQuantity>1</cbc:InvoicedQuantity>
    <cbc:LineExtensionAmount currencyID="COP">1000000.00</cbc:LineExtensionAmount>
    <cac:TaxTotal>
      <cbc:TaxAmount currencyID="COP">90000.00</cbc:TaxAmount>
      <cbc:TaxEvidenceIndicator>false</cbc:TaxEvidenceIndicator>
      <cac:TaxSubtotal>
        <cbc:TaxableAmount currencyID="COP">1000000.00</cbc:TaxableAmount>
        <cbc:TaxAmount currencyID="COP">90000.00</cbc:TaxAmount>
        <cac:TaxCategory>
          <cbc:Percent>9.00</cbc:Percent>
          <cac:TaxScheme>
            <cbc:ID>01</cbc:ID>
            <cbc:Name>IVA</cbc:Name>
          </cac:TaxScheme>
        </cac:TaxCategory>
      </cac:TaxSubtotal>
    </cac:TaxTotal>
    <cac:Item>
      <cbc:Description>auto</cbc:Description>
    </cac:Item>
    <cac:Price>
      <cbc:PriceAmount currencyID="COP">1000000.00</cbc:PriceAmount>
    </cac:Price>
  </cac:InvoiceLine>
</Invoice>
php
Martin Hope
moneyBox
Asked: 2020-02-20 13:15:30 +0800 CST
  • 1

I am connecting to a WSLD SOAP service where it is necessary to use MTOM to send attached information, I am trying to upload a ZIP file in base64 but the server returns the error that it cannot find the information of the message, that is, of the attachment, then I will indicate what that I send to the server using cURL in PHP to see if someone can guide me in what I am sending wrong that does not allow the server to read the attached document.

Error Message: Could not create message from InputStream: Unable to internalize message; nested exception is com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message

POST /ruta/portal.wsdl HTTP/1.1
Host: empresa.com
Accept: */*
User-Agent: PHP-7
Content-Type: multipart/related; type="application/xop+xml"; start="<[email protected]>"; start-info="text/xml"; boundary="------=_Part_1_363f118.a4e1f4f9730a01986d6c6fb8e9663303"
Content-Length: 28908
Expect: 100-continue

------=_Part_1_363f118.a4e1f4f9730a01986d6c6fb8e9663303
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID: <[email protected]>

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rep="http://www.empresa.com/ruta/EnvioDocumentos">
    <soapenv:Header>
        <wsse:Security soapenv:mustunderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsse:UsernameToken wsu:id="UsernameToken-2">
                <wsse:Username>xxxxxxxxx</wsse:Username>
                <wsse:Password type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile1.0#PasswordText">xxxxx</wsse:Password>
                <wsse:Nonce encodingtype="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security1.0#Base64Binary">zzzzzzzzzz</wsse:Nonce>
                <wsu:Created>2019-02-19T16:07:47.000Z</wsu:Created>
            </wsse:UsernameToken>
        </wsse:Security>
    </soapenv:Header>
    <soapenv:Body>
        <rep:EnvioDocumento>
            <rep:Document><inc:Include href="cid:363f118a4e1f4f9730a01986d6c6fb8e96633032" xmlns:inc="http://www.w3.org/2004/08/xop/include"/></rep:Document>
        </rep:EnvioDocumento>
    </soapenv:Body>
</soapenv:Envelope>


------=_Part_1_363f118.a4e1f4f9730a01986d6c6fb8e9663303
Content-Type: application/zip; name="archivo_003a699d00.zip"
Content-Transfer-Encoding: base64
Content-ID: <363f118a4e1f4f9730a01986d6c6fb8e96633032>
Content-Disposition: attachment; name="archivo_003a699d00.zip" filename="archivo_003a699d00.zip"

UEsD....Datos_en_Base64.....zA3
------=_Part_1_363f118.a4e1f4f9730a01986d6c6fb8e9663303--
php
Martin Hope
moneyBox
Asked: 2020-02-14 15:34:43 +0800 CST
  • 1

Good day.

I am trying to upload an invoice to the webservice of the DIAN (tax entity in Colombia), previously I had created a publication for the part of the "WSS authentication" which was solved, but now the problem is that the webservice of the DIAN throws the error: Unexpected error [null] processing incoming WS request .

I have already investigated with the same DIAN but they never respond, if someone has already seen the topic and is connecting to the service, I would appreciate your response, I leave you the Request and Response:

The Request sent is:

POST /habilitacion/B2BIntegrationEngine/FacturaElectronica/facturaElectronica.wsdl HTTP/1.1
Host: facturaelectronica.dian.gov.co
Accept: */*
User-Agent: moneyBox
Content-Type: text/xml; charset=UTF-8
Content-Length: 28198
Expect: 100-continue
<!--?xml version="1.0" encoding="UTF-8"?-->
<soapenv:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rep="http://www.dian.gov.co/servicios/facturaelectronica/ReportarFactura">
    <soapenv:header>
        <wsse:security soapenv:mustunderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsse:usernametoken wsu:id="UsernameToken-2">
                <wsse:username>d8xxxxxx-exxx-4xxx-axxx-aaxxxxxxxxxa</wsse:username>
                <wsse:password type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile1.0#PasswordText">e098cxxxxxxxxxxxxxxxx4501b5</wsse:password>
                <wsse:nonce encodingtype="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security1.0#Base64Binary">bW9xxxxxxxxxDcwNA==</wsse:nonce>
                <wsu:created>2019-02-13T12:25:04.000Z</wsu:created>
            </wsse:usernametoken>
        </wsse:security>
    </soapenv:header>
    <soapenv:body>
        <rep:enviofacturaelectronicapeticion>
            <rep:nit>700xxxxxx</rep:nit>
            <rep:invoicenumber>980000000</rep:invoicenumber>
            <rep:issuedate>2019-02-13T12:25:04</rep:issuedate>
            <rep:document>UEs...El_Zip_en_Base64....uMjcwNw==</rep:document>
        </rep:enviofacturaelectronicapeticion>
    </soapenv:body>
</soapenv:envelope>

And the response:

HTTP/1.1 100 Continue
HTTP/1.1 200 OK
Date: Wed, 13 Feb 2019 17:25:08 GMT
Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
SOAPAction: ""
Content-Type: Multipart/Related; start-info="text/xml"; type="application/xop+xml"; boundary="----=_Part_356292_546049942.1550078708580"
Set-Cookie: TS0133d910=01ca0e1ef651253b25b49afd1557f600dec2280bb5852510eeffa34063be7fa62f74d86b09c95f04d731f25eb78b11362ff2483058; Path=/
Transfer-Encoding: chunked
------=_Part_356292_546049942.1550078708580
Content-Type: application/xop+xml; charset=utf-8; type="text/xml"
<soap-env:envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
    <soap-env:header>
        <wsse:security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" soap-env:mustunderstand="1">
        ..... muchas etiquetas del Firmado Digital... (Signature)
        </wsse:security>
    </soap-env:header>
    <soap-env:body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:id="id-352783">
        <ns2:enviofacturaelectronicarespuesta xmlns:ns2="http://www.dian.gov.co/servicios/facturaelectronica/ReportarFactura" xmlns:ns3="http://www.dian.gov.co/servicios/facturaelectronica/ConsultaDocumentos" xmlns:ns4="http://www.dian.gov.co/servicios/facturaelectronica/VersionDespliegue">
            <ns2:version>Componente DIAN</ns2:version>
            <ns2:receiveddatetime>2019-02-13T12:25:06.924-05:00</ns2:receiveddatetime>
            <ns2:responsedatetime>2019-02-13T12:25:08.567-05:00</ns2:responsedatetime>
            <ns2:response>100</ns2:response>
            <ns2:comments>Error [null] inesperado al procesar la solicitud WS entrante..</ns2:comments>
        </ns2:enviofacturaelectronicarespuesta>
    </soap-env:body>
</soap-env:envelope>
------=_Part_356292_546049942.1550078708580--
php
Martin Hope
moneyBox
Asked: 2020-02-13 08:24:31 +0800 CST
  • 0

I'm on PHP and through a cURL connection I'm receiving SOAP type frames, but I can't find a way to extract the information of interest and then use it.

This is what I receive:

HTTP/1.1 100 Continue
HTTP/1.1 200 OK
Date: Tue, 12 Feb 2019 16:05:50 GMT
Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
SOAPAction: ""
Content-Type: Multipart/Related; start-info="text/xml"; type="application/xop+xml"; boundary="----=_Part_11693774_xx"
Set-Cookie: TS0133d910=01ca0e1ef6f6e600a5e5f544e580e222d153067bfe4f637ee1fae74f525abcb50681cbd0c3769c51e7a9ab7204cb7a7f2235a061ed; Path=/
Transfer-Encoding: chunked
------=_Part_11693774_xx
Content-Type: application/xop+xml; charset=utf-8; type="text/xml"
<soap-env:envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
    <soap-env:header>
        <wsse:security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" soap-env:mustunderstand="1">
        .... DATA....
        </wsse:security>
    </soap-env:header>
    <soap-env:body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:id="id-11265519">
        .... MAS DATA....
    </soap-env:body>
</soap-env:envelope>
------=_Part_11693774_xx--

As you can see after the headers there is no typical double line break ( \n\n ) that basically allows me to extract the data and omit the headers, so using str_ireplace I have managed to extract a certain part, but not all :( .

My goal is to extract the data between ------=_Part_11693774_xx and ------=_Part_11693774_xx-- , and then convert it to accessible XML with simplexml_load_string() .

This is what I have coded:

<?php
class Algo{
    private $r=NULL;
    private $data=NULL;

    public function debugResponse() {
        $a= str_ireplace(['SOAP-ENV:', 'SOAP:'], '', $this->r);
        $b= '<Data>'. $a. '</Data>';
        $sxml= simplexml_load_string($b);

        print_r($b);
        echo "<br><br>Info..<br>";
        print_r($sxml);
        $this->data= $sxml;
        unset($sxml, $a, $b);
    }

    public function resultado() {
        return $this->data;
    }

    public function exec() {
        /* conexion cURL */
        $this->r= curl_exec($s);
        $this->debugResponse();
    }
}

$a= new Algo();
echo 'Datos:<br>'. $a->resultado();
?>

And it returns me:

HTTP/1.1 100 Continue
HTTP/1.1 200 OK
Date: Tue, 12 Feb 2019 16:05:50 GMT
Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
SOAPAction: ""
Content-Type: Multipart/Related; start-info="text/xml"; type="application/xop+xml"; boundary="----=_Part_11693774_xx"
Set-Cookie: TS0133d910=01ca0e1ef6f6e600a5e5f544e580e222d153067bfe4f637ee1fae74f525abcb50681cbd0c3769c51e7a9ab7204cb7a7f2235a061ed; Path=/
Transfer-Encoding: chunked
------=_Part_11693774_xx
Content-Type: application/xop+xml; charset=utf-8; type="text/xml"
<envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
    <header>
        <wsse:security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" mustunderstand="1">
        .... DATA....
        </wsse:security>
    </header>
    <body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:id="id-11265519">
        .... MAS DATA....
    </body>
</envelope>
------=_Part_11693774_xx--

In this case the last line ------=_Part_11693774_xx-- does not allow me to convert it to XML, because I already did the manual process, remove that last line and now the XML is assembled with the important parts accessible.

---- Edited 02/12/19, 12:49

I have managed to extract the data omitting the headers, but curiously simplexml_oad_string() does not arm the object for me, I leave you the code and result:

<?php
$a= str_ireplace(['SOAP-ENV:', 'SOAP:'], '', $this->r);
$pos= stripos($a, "<envelope");
$pos2= stripos($a, "</envelope>")+strlen('</envelope>');
$b= '<?xml version="1.0" encoding="UTF-8"?><data>'.substr($a, $pos, ($pos2-$pos)).'</data>';
$sxml= simplexml_load_string($b);
print_r($sxml);
?>

And result:

SimpleXMLElement Object
( [Envelope] => SimpleXMLElement Object ( [Header] => SimpleXMLElement Object ( ) [Body] => SimpleXMLElement Object ( ) )
)
php
Martin Hope
moneyBox
Asked: 2020-01-24 13:18:56 +0800 CST
  • 4

With the poor documentation that exists regarding the implementation with the WebService yesterday and today I exhausted my resources to investigate the error that I am receiving, and assuming that the same DIAN (Tax entity in Colombia) does not answer the phones (I was hung up for 2 hours and nothing ...) and much less the emails because I put here the question if someone can help me and in the same way it helps any programmer who is in the same situation.

When submitting the invoice I receive an error stating " JBWEB000120: The request sent by the client was syntactically incorrect ".

I pass the complete Request and Respose:

POST /habilitacion/B2BIntegrationEngine/FacturaElectronica HTTP/1.0
Host: facturaelectronica.dian.gov.co
User-Agent: NuSOAP/0.9.5 (1.123)
Content-Type: text/xml; charset=UTF-8
SOAPAction: ""
Content-Length: 28319
<soap-env:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rep="http://www.dian.gov.co/servicios/facturaelectronica/ReportarFactura" xmlns:ns2323="http://tempuri.org">
    <soap-env:header>
        <wsse:security soapenv:mustunderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsse:usernametoken wsu:id="UsernameToken-2">
                <wsse:username>d8xxx-exxx-4xxx-axxx-aaxxxx</wsse:username>
                <wsse:password type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile1.0#PasswordText">a8bxxxxHash265xxxxxx99</wsse:password>
                <wsse:nonce encodingtype="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security1.0#Base64Binary">bW9uxxxxxxxxxxxxxxUyNg==</wsse:nonce>
                <wsu:created>2019-01-23T16:08:39-06:00</wsu:created>
            </wsse:usernametoken>
        </wsse:security>
    </soap-env:header>
    <soap-env:body>
        <rep:enviofacturaelectronicapeticion>
            <rep:nit>700xxxx</rep:nit>
            <rep:invoicenumber>980000000</rep:invoicenumber>
            <rep:issuedate>2019-01-23T16:08:39-06:00</rep:issuedate>
            <rep:document>UEsDBBQA.....AuMS4yNzA3</rep:document>
        </rep:enviofacturaelectronicapeticion>
    </soap-env:body>
</soap-env:envelope>

And the response:

<title>JBoss Web/7.4.8.Final-redhat-4 - JBWEB000064: Error report</title>
<h1>JBWEB000065: HTTP Status 400 - </h1>
<p><b>JBWEB000309: type</b> JBWEB000067: Status report</p>
<p><b>JBWEB000068: message</b> <u></u></p>
<p><b>JBWEB000069: description</b> <u>JBWEB000120: The request sent by the client was syntactically incorrect.</u></p>

---- Edited 2019/01/30, 15:38. I made some changes to the NuSOAP library since when sending the information it passed everything to lowercase (strtolower()), so I removed the use of the strtolower() function in everything that consisted of sending , and the error now changed, I He says:

HTTP/1.0 302 Found Location: https://facturaelectronica.dian.gov.co/habilitacion/B2BIntegrationEngine/FacturaElectronica Server: BigIP Connection: close Content-Length: 0

The problem persists :(....

---- Edited 2019/01/31, 13:15. After trying with SOAPUI I realized that the main problem is the NuSOAP libraries, so due to the time I have wasted on this and contemplating that it seems more feasible to make the code in Socket by putting together the frame to verify if there are problems with the WebService of the DIAN I have chosen to assemble it by hand.

I coded it and just realized that for some unknown reason NuSOAP does other things that throw the error mentioned at the beginning. Right now I'm talking to the DIAN because I'm sending the frame manually as required by the WebService and it keeps giving me the error:

Client The security token could not be authenticated or authorized; nested exception is org.apache.ws.security.WSSecurityException: The security token could not be authenticated or authorized

And the code that I have so far for the tests by hand is:

<?php
public function createXML() {
        # crea el XML SOAP
    }

public funciton getXML() {
        # retorna el xml con $xml->saveXML();
    }

public function sendToDIAN($wsUrl) {
            $this->createXML();
            $s= curl_init();
            curl_setopt($s, CURLOPT_URL, $wsUrl);
            curl_setopt($s, CURLOPT_HTTPHEADER, array("User-Agent: moneyBox", "Content-Type: text/xml; charset=UTF-8", "SOAPAction:", "Content-Length: ". strlen($this->getXML())) );
            curl_setopt($s, CURLOPT_HEADER, 1 );
            curl_setopt($s, CURLOPT_POST, 1);
            curl_setopt($s, CURLOPT_POSTFIELDS, $this->getXML());
            curl_setopt($s, CURLOPT_RETURNTRANSFER, true);
            curl_setopt($s, CURLOPT_VERBOSE, TRUE);
            curl_setopt($s, CURLINFO_HEADER_OUT, true);
            $resp= curl_exec($s);
            $rq= curl_getinfo($s);

            echo "<br>WS: ". $wsUrl;
            echo "<br>XML:<br>";
            print_r($this->getXML());
            echo "<br>Request:<br>";
            print_r($rq["request_header"]);
            echo "<br><br>Response:<br>";
            print_r($resp);
?>

The request is:

POST /habilitacion/B2BIntegrationEngine/FacturaElectronica/facturaElectronica.wsdl HTTP/1.1
Host: facturaelectronica.dian.gov.co
Accept: */*
User-Agent: PHP
Content-Type: text/xml; charset=UTF-8
Content-Length: 28198
Expect: 100-continue

<!--?xml version="1.0" encoding="UTF-8"?-->
<soapenv:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rep="http://www.dian.gov.co/servicios/facturaelectronica/ReportarFactura">
    <soapenv:header>
        <wsse:security soapenv:mustunderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsse:usernametoken wsu:id="UsernameToken-2">
                <wsse:username>d8xxx-exxx-4xx0-axx2-aa4xxxxxda</wsse:username>
                <wsse:password type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile1.0#PasswordText">2fb7a2xxxxxxxxe6de4a</wsse:password>
                <wsse:nonce encodingtype="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security1.0#Base64Binary">bW9xxxxxMTU1MA==</wsse:nonce>
                <wsu:created>2019-01-31T14:05:50.000Z</wsu:created>
            </wsse:usernametoken>
        </wsse:security>
    </soapenv:header>
    <soapenv:body>
        <rep:enviofacturaelectronicapeticion>
            <rep:nit>700xxxx7</rep:nit>
            <rep:invoicenumber>980000000</rep:invoicenumber>
            <rep:issuedate>2019-01-31T14:05:50</rep:issuedate>
            <rep:document>UEsDBB....jEuMjcwNw==</rep:document>
        </rep:enviofacturaelectronicapeticion>
    </soapenv:body>
</soapenv:envelope>

The Response is:

HTTP/1.1 100 Continue
HTTP/1.1 500 Internal Server Error
Date: Thu, 31 Jan 2019 19:05:51 GMT
Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
SOAPAction: ""
Content-Type: text/xml;charset=utf-8
Content-Length: 443
X-Cnection: close
Set-Cookie: TS0133d910=01ca0e1ef6f0097a1348704194309a4e9b294fed9c0bcca644e4ae8558c221f7f76b430cee909654460964cd09e1ac5affe8cd8d04; Path=/

<soap-env:envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
    <soap-env:header></soap-env:header>
    <soap-env:body>
        <soap-env:fault>
            <faultcode>SOAP-ENV:Client</faultcode>
            <faultstring xml:lang="en">The security token could not be authenticated or authorized; nested exception is org.apache.ws.security.WSSecurityException: The security token could not be authenticated or authorized</faultstring>
        </soap-env:fault>
    </soap-env:body>
</soap-env:envelope>
php