Authentication

The Gosocket OSE Web Service uses WS-Security UsernameToken to authenticate each request. The token must be included in the SOAP header of all methods — sendBill, sendSummary, getStatus and getStatusCdr.

Token structure

AtributoTipoDescripción

UsernamestringIssuer's RUC concatenated with the SOL username, without separators. Example: 20556695548CLHBIHCVK

PasswordstringSOL password in plain text. The Type attribute must be PasswordText.

Example

WS-Security Header

<SOAP-ENV:Header>
<ns2:Security
  xmlns:ns2="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
  <ns2:UsernameToken>
    <ns2:Username>20556695548CLHBIHCVK</ns2:Username>
    <ns2:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">
      x#1F^BTAn(3t
    </ns2:Password>
  </ns2:UsernameToken>
</ns2:Security>
</SOAP-ENV:Header>

Incorrect credentials

If the Username or the Password are incorrect, the OSE will return a 0102 error with the message "Incorrect username or password". Confirm that the credentials provided by Gosocket are correct and active.

Required namespaces

The header must declare the xmlns:ns2 namespace pointing to the WS-Security specification. Without this namespace the SOAP message will be invalid.