Vigicap
Connector
FreeIPA
API credential, entered client by client.
Self-hosted identity directory for Linux fleets (LDAP + Kerberos), used by MSPs as the central account repository on a client's Linux servers/workstations. Vigicap reads the number of user accounts and the number of enrolled OTP tokens to evaluate the ReCyF objectives « Gestion des identités et des accès » and « Authentification multi-facteurs » — a coverage estimate, not an exhaustive per-user audit.
Beta01
What to create in the tool
The access is created in FreeIPA, 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 FreeIPA account (or a dedicated one, a member of the admins group or with at least read rights on users and OTP tokens) for the connector. FreeIPA authenticates with a username + password, with no dedicated API token — prefer a dedicated service account over a personal administrator account.
Minimum role
The minimum role this connector needs is not documented to date. We would rather write that than guess it: an unverified claim about access rights ends up in front of a client's data protection officer, who is precisely the person who will check it. Refer to the vendor's documentation, which alone is authoritative on its role model.
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
FreeIPA username (uid) of the account used for reads.
vigicap-connector
- Passwordsecret
Password for the username above.
Mot de passe FreeIPA
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 was written from the vendor's documented API and has not yet been run against a real instance. It is marked “Beta” everywhere it appears.
The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.