Connector

Okta

API credential, entered client by client.

SaaS identity provider: account directory, single sign-on and second factor across a company's applications. Vigicap reads how many accounts exist and in what state, and whether at least one second-factor enrolment policy is active, to assess the ReCyF objectives on identity management and multi-factor authentication. The exact scope of an MFA policy is not evaluated.

What to create in the tool

The access is created in Okta, 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

Dans la console Okta : Security > API > Tokens > Create Token. Le jeton n'est affiché qu'une seule fois. L'URL à saisir est celle de votre organisation (par exemple https://votre-entreprise.okta.com, ou votre domaine personnalisé). Un jeton Okta expire après 30 jours sans utilisation : une synchronisation régulière le maintient valide.

Minimum role

Créez un jeton d'API (Security > API > Tokens) sur un compte de service disposant du rôle « Read-Only Administrator ». Ce connecteur n'appelle que GET /api/v1/users et GET /api/v1/policies. Le jeton hérite des droits du compte qui le crée : ne le générez jamais depuis le compte d'un super-administrateur humain.

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

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.

Jeton d'API Oktasecret
Créé dans Security > API > Tokens, depuis un compte de service en lecture seule.
00a1B2c3...

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.

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.

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