ImpactECS REST API Administration

Signed in as

Sign in to continue

Sign in with the work account that has been granted the ImpactECS REST API administrator role. Mappings cannot be viewed or changed without it.

Loading

Administrator access required

Nothing you had typed in the form was saved.

Identity mappings

Filter mappings

No connectors are configured yet

Mappings cannot be created until 3C Software configures at least one connector for this deployment. Contact 3C Software support.

No mappings yet

Every caller is refused until an Azure identity is mapped to a connector.

No matches

Azure identities and the connector each one runs as
Azure identity	Connector	Certificate thumbprints (SHA-256)	Actions

Add mapping

Theirs
Yours

Azure identity The Application (client) ID of the caller's Entra ID app registration, exactly as it appears in the Azure portal and in the token — for example 6f1c9d24-7b3a-4e51-9c0d-2f8ab41d77e2. An identity cannot be changed. Delete this mapping and add another to move it.

Connector A connector is the ImpactECS account the call runs as — it decides which models and data the caller can reach. Only connectors 3C Software has configured for this deployment appear here.

Certificate thumbprint, SHA-256 (optional) 64 hexadecimal characters. Spaces and colons are accepted and removed. Leave both slots empty to accept this identity without pinning it to a client certificate.

Second certificate thumbprint, SHA-256 (optional) Use this slot to rotate a certificate: add the new thumbprint here, switch the client over, then remove the old one from the first slot.