Skip to content

Aclarar el requisito del formato del certificado en PEM #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nroxDev wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Aclarar el requisito del formato del certificado en PEM #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -233,6 +233,22 @@ class InvoiceAeatController extends Controller
>
> Si el certificado no es válido o hay error de validación, el array tendrá 'status' => 'error' y 'message'.

#### Problema conocido: certificados `.p12`

Si el certificado configurado está en formato `.p12` (en lugar de `.pem`), la librería SOAP no puede cargar el WSDL y devuelve un error como:

```bash
"SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://prewww2.aeat.es/static_files/common/internet/dep/aplicaciones/es/aeat/tikeV1.0/cont/ws/SistemaFacturacion.wsdl' : failed to load external entity "https://prewww2.aeat.es/static_files/common/internet/dep/aplicaciones/es/aeat/tikeV1.0/cont/ws/SistemaFacturacion.wsdl"\n",
```

Convierte el certificado `.p12` a PEM (certificado y clave) antes de configurarlo:

```bash
openssl pkcs12 -in certificado.p12 -out certificado.pem -clcerts -nokeys
openssl pkcs12 -in certificado.p12 -out certificado.key -nocerts -nodes
```


---

## Validación y creación de Breakdown (Ejemplo de Controller)
Expand Down