> For the complete documentation index, see [llms.txt](https://docs.afipsdk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.afipsdk.com/recursos/tutoriales-pagina-de-arca/autorizar-web-service-de-testing.md).

# Autorizar web service de testing

{% hint style="info" %}
Si querés evitar este trabajo manual, podés hacerlo automáticamente a través de tu sistema con la [automatización para Autorizar web service de desarrollo](https://afipsdk.com/docs/automations/auth-web-service-dev/nodejs/).
{% endhint %}

Para que los certificados puedan acceder a un web service se debe crear una autorización, esto se hace de la siguiente manera:

Dentro de **«WSASS - Autogestión Certificados Homologación»**, que anteriormente en [Obtener certificado de testing](/recursos/tutoriales-pagina-de-arca/obtener-certificado-de-testing.md#paso-4-generar-el-certificado-cert) explicamos cómo ingresar, debemos ir a «Crear autorización a servicio»

<figure><img src="https://4026677166-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVEAVwm5cCW83gSe7NH8Z%2Fuploads%2Fgit-blob-20d88653d8491a35c4c4c644b3bcd455d7fe1694%2Fimagen.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

Allí dentro en `1. Nombre simbólico del DN a autorizar` debemos seleccionar el certificado que queremos autorizar.

En `3. CUIT representado` debemos ingresar el CUIT con el cual queremos utilizar el web service. En modo testing recomendamos usar el CUIT propio para no crear confusión.

Y en `5. Servicio al que desea acceder` debemos elegir el web service a utilizar.\`

Con todo esto listo debemos presionar en «Crear autorización de acceso»

Por ejemplo para autorizar al Web service de factura electrónica me quedaría así

<figure><img src="https://4026677166-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVEAVwm5cCW83gSe7NH8Z%2Fuploads%2Fgit-blob-a36644fc8def0b0ba78c026eca1908fbf05657d5%2Fimagen.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

Luego ingresamos en «Autorizaciones» para verificar que se creó la autorización correctamente

<figure><img src="https://4026677166-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVEAVwm5cCW83gSe7NH8Z%2Fuploads%2Fgit-blob-b9ed04974637a6d6c4f58acc53909182aff784bf%2Fimagen.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

Eso sería todo, ya estamos listos para usar el certificado con el web service autorizado


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.afipsdk.com/recursos/tutoriales-pagina-de-arca/autorizar-web-service-de-testing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.