> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-api/joint-resolution-6-api/using-mtls.md).

# Using mTLS

{% hint style="warning" %}
**Deprecated Section:** This section is deprecated! For new integrations or migrations, please use the [new documentation](/caf-api/connect/authentication/using-mtls.md).
{% endhint %}

The use of Mutual Transport Layer Security (mTLS) in integration with the Joint Resolution 6 solution provides an additional layer of security and authentication, ensuring secure communication between clients and our services. To access the Joint Resolution 6 solution through mTLS, clients must possess a certificate signed by the Caf for mutual authentication.

This guide provides step-by-step instructions on how to configure and use mTLS to access our solution:

1. **Certificate submission**\
   Client: Send the required certificate for mTLS authentication to the Caf through Keeper, using the designated folder `mTLS Origin Cert`.
2. **Certificate signing**\
   Caf: Upon receiving the certificate, the Caf performs the necessary signing for validation.
3. **Receipt of signed certificate**\
   Client: The Caf sends the signed certificate back to the client, using Keeper and the designated folder `mTLS Signed Cert`.
4. **Use of signed certificate**\
   Client: With the signed certificate in hand, the client can now use it for authentication and access to the Joint Resolution 6 solution.

Then, make sure to change the base URL:

{% code title="Base URL:" %}

```url
https://mtls.prd.combateafraude.com
```

{% endcode %}

This guide provides a simplified overview of the process of using mTLS to access the Joint Resolution 6 solution, highlighting the importance of security in the communication between clients and our services. Be sure to carefully follow each step to ensure a successful integration.

For any questions or technical issues, do not hesitate to contact our technical support team.


---

# 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.caf.io/caf-api/joint-resolution-6-api/using-mtls.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.