Skip to main content
Back to the connector catalogue

Connector

Keycloak

API credential, entered client by client.

Self-hosted identity and SSO server (OIDC/SAML), used by MSPs as a centralised identity provider for their clients. Vigicap reads the number of users provisioned on the realm as well as the required-actions configuration (two-factor authentication enforced by default) to evaluate the ReCyF objectives « Gestion des identités et des accès » and « Authentification multi-facteurs ».

01

What to create in the tool

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

In Keycloak: Clients > Create client > check "Client authentication" (confidential client) and enable "Service accounts roles". Service accounts roles tab > Assign role > client realm-management > add view-users, query-users and view-realm. The Client Secret is on the client's Credentials tab.

Minimum role

Service account avec exactement view-users, query-users et view-realm sur realm-management — aucune écriture.

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.

  • Realm

    Name of the Keycloak realm to assess (not "master", unless it is the client's own realm).

    client-realm

  • Client ID

    Confidential client with "Service accounts roles" enabled.

    vigicap-connector

  • Client Secretsecret

    Client's Credentials tab.

    Client Secret

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.