Skip to main content
Vigicap
Try it
Back to the connector catalogue

Connector

privacyIDEA

API credential, entered client by client.

Self-hosted, open-source multi-factor authentication (MFA) server, used by MSPs as a centralised OTP token backend (VPN, SSO, business applications). Vigicap reads the number of tokens enrolled and active on the server to evaluate the ReCyF objective « Authentification renforcée (MFA) ». The presence of active tokens proves that MFA capability is deployed, but not that it is enforced on all of the client's accounts.

01

What to create in the tool

The access is created in privacyIDEA, not in Vigicap. Vigicap never asks for an administrator's password: it expects an API credential that you create, that you can see, and that you can revoke without us.

Where to generate it

Use an existing privacyIDEA administrator account (Config > Administrators in the web interface), or create a dedicated read-only one — Vigicap only needs to list tokens via /token/.

Minimum role

Un administrateur dédié (Config > Administrators) couvert par une policy de périmètre « admin » n'accordant que l'action « tokenlist » : les policies admin de privacyIDEA fonctionnent en liste blanche, ce compte ne peut donc rien faire d'autre que lister les jetons.

Taken from the vendor's own role model, and checked before publication.

02

What to enter in Vigicap

The exact fields of the connection form, in the order they appear. Values marked “secret” never travel back to the browser: they are encrypted at rest and deleted on disconnection.

The form starts with the instance address, entered separately from the fields below. The public catalogue does not yet publish whether this connector needs one, or what it looks like — so this list is exact about everything else, and silent about that first field.

  • Usernamesecret

    privacyIDEA administrator account (Config > Administrators).

    admin

  • Passwordsecret

    Password for the administrator account above.

    Mot de passe administrateur

03

Per-client routing

The connection is made client by client: one credential per client, entered on that client's record. Nothing is shared between two clients, and disconnecting one leaves the other untouched.

04

What it does, and what it does not do

ReCyF objectives it pre-fills

A reading feeds one objective of the ANSSI ReCyF framework. It PROPOSES it: the level only counts once a consultant has confirmed it.

  • #10 Gestion des identités et des accès des utilisateurs aux systèmes d'informationManagement of user identities and of user access to the information systems

Read-only

The reads are read-only: Vigicap writes nothing into the tool while reading it.

What is read, what is kept, for how long and with which rights: the same register, connector by connector, in the data inventory.

Verification

This connector has been run end to end against a real instance of the tool, not merely tested against a mock.

The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.