> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/tech-fr/9.2/integration-okta.md).

# Intégration Okta

## Aperçu <a href="#apercu" id="apercu"></a>

Cette section fournit des instructions sur l'intégration Okta.

{% hint style="info" %}
Dans les instructions, remplacez `<workflowgen url>` par le domaine et le chemin de votre instance de WorkflowGen; par exemple, `localhost/wfgen` ou `macompagnie.com/wfgen`.
{% endhint %}

{% content-ref url="/pages/k07HEjpyGWCbQffN5sDr" %}
[Authentification](/tech-fr/9.2/integration-okta/authentification.md)
{% endcontent-ref %}

Comment configurer l'authentification WorkflowGen avec Okta

{% content-ref url="/pages/ogXtpSQRFg2GGb8t4zGj" %}
[Approvisionnement des utilisateurs](/tech-fr/9.2/integration-okta/approvisionnement-des-utilisateurs.md)
{% endcontent-ref %}

Comment créer un annuaire avec le connecteur d'auto-approvisionnement

{% content-ref url="/pages/HxzAK1VJI1LzOACX8s5d" %}
[WorkflowGen Plus v2](/tech-fr/9.2/integration-okta/workflowgen-plus-v2.md)
{% endcontent-ref %}

Comment configurer l'authentification déléguée pour l'application mobile WorkflowGen Plus v2 à l'aide d'Okta

{% content-ref url="/pages/cLDVZK8S3i4VhcdkRH06" %}
[Scripts côté serveur](/tech-fr/9.2/integration-okta/scripts-cote-serveur.md)
{% endcontent-ref %}

Comment autoriser WorkflowGen pour accéder aux scripts côté serveur à l'aide d'Okta

{% content-ref url="/pages/GLIMYn8tn3UyPNdcn3Ap" %}
[Applications monopage](/tech-fr/9.2/integration-okta/applications-monopage.md)
{% endcontent-ref %}

Comment autoriser WorkflowGen pour accéder aux applications monopage à l'aide d'Okta

{% content-ref url="/pages/tQoPShwv02Gmnx2RZyoo" %}
[CLI WorkflowGen](/tech-fr/9.2/integration-okta/cli-workflowgen.md)
{% endcontent-ref %}

Comment autoriser l'accès Okta à l'interface de ligne de commande (CLI) WorkflowGen

{% content-ref url="/pages/zd6BqdYUvsi3yL76Er6R" %}
[Génération d'un lien universel](/tech-fr/9.2/integration-okta/generation-dun-lien-universel.md)
{% endcontent-ref %}

Comment générer un lien universel pour simplifier la connexion à l'application mobile WorkflowGen Plus

{% content-ref url="/pages/GygjCtFPEiIN6hN5cu0G" %}
[Informations supplémentaires](/tech-fr/9.2/integration-okta/informations-supplementaires.md)
{% endcontent-ref %}

Informations supplémentaires sur le support des services SOAP API de WorkflowGen et le support des applications de type service Web


---

# 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.workflowgen.com/tech-fr/9.2/integration-okta.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.