Skip to main content
Back to the connector catalogue

Connector

JumpCloud

API credential, entered client by client.

Cloud directory used in place of Active Directory: accounts, device binding and second factor in one place. Vigicap reads how many accounts exist, how many are suspended and how many have a second factor configured, to assess the ReCyF objectives on identity management and multi-factor authentication. This reading says a factor is configured, never that it is required at every sign-in.

01

What to create in the tool

The access is created in JumpCloud, 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 JumpCloud : Administrators > créez un administrateur en lecture seule dédié à Vigicap, puis ouvrez son profil et générez sa clé d'API. Aucune URL n'est à saisir : JumpCloud n'a qu'un seul domaine pour tous ses clients.

Minimum role

Créez une clé d'API depuis un compte administrateur disposant du rôle « Read-only Administrator » (Administrators > ajouter un administrateur, rôle lecture seule), puis récupérez sa clé dans son profil. Ce connecteur n'appelle que GET /systemusers. Une clé JumpCloud hérite des droits de l'administrateur qui la détient : ne réutilisez jamais celle d'un administrateur humain ayant les pleins pouvoirs.

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.

  • Clé d'API JumpCloudsecret

    Générée dans le profil d'un administrateur en lecture seule dédié.

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.

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