Scoped roles
Scoping happens in two steps: first you assign the service principal its base roles, then you can optionally restrict what any individual credential or trust is allowed to use.Step 1: Assign base roles
On the service principal’s Details tab, the Role field assigns one or more of C1’s standard roles to the service principal — the same roles you’d assign to a human user. See User roles for the full list and descriptions of each role.Step 2: Scope a credential or trust (optional)
Every credential and federation trust can be limited to a subset of the service principal’s roles. The effective permissions are the intersection of:- The roles assigned to the service principal
- The scoped roles on the credential or trust
IP allowlists
Both credentials and federation trusts support IP address restrictions. When configured, only requests from the specified IP ranges are accepted.- Add up to 32 IP address ranges per credential or trust
- Leave empty to allow all IPs
- Supports both IPv4 and IPv6 (enter ranges like
192.168.1.0/24or2001:db8::/32)
The same rules apply everywhere you set allowed source IPs: the tenant IP allowlist settings, personal API keys, service principal credentials, and workload federation trusts. If an entry is invalid, such as an IPv4-mapped IPv6 address like
::ffff:192.0.2.1, C1 keeps it in the field so you can correct it, and you can’t save until you fix or remove it. Enter IPv4 addresses in IPv4 notation instead.IP allowlists work best with self-hosted runners or fixed egress IPs. GitHub-hosted runners use thousands of IP ranges that change frequently, making IP restrictions impractical for them.
Credential expiration
Credentials expire after a set duration:
Expired credentials can’t issue new tokens. Plan credential rotation before expiry. See credential rotation for a zero-downtime rotation procedure.
Credential expiration can’t be extended. Create a new credential with the desired expiration and revoke the old one.
DPoP (Demonstrating Proof-of-Possession)
DPoP (RFC 9449) binds access tokens to a specific cryptographic key. Even if a token is intercepted, it can’t be used without the corresponding private key. Enable DPoP when creating a credential by toggling Require DPoP. When enabled:- The client must include a
DPoPproof header with every token request - Issued tokens are type
DPoPinstead ofBearer - API requests must include both the token and a fresh DPoP proof
CEL conditions (federation)
Federation trusts use CEL (Common Expression Language) expressions to control which tokens are accepted. The expression is evaluated against the JWT claims and must returntrue.
For GitHub Actions, GitLab CI, HCP Terraform, AWS IAM, and SPIFFE, the trust wizard collects structured fields (for example organization, repository, branch) and generates the CEL expression for you. Switch to manual mode to write your own expression. Custom OIDC providers have no structured wizard — you write the CEL expression directly. See set up federation for the wizard walkthrough.
CEL environment
The CEL environment exposes:claims— a map of all decoded JWT claims
contains(), startsWith(), endsWith(), matches(), size().
Example expressions
Writing expressions
- Expressions are limited to 1,024 bytes
- Always validate the
subclaim or an equivalent identifier - Use additional claims for defense-in-depth scoping
System log events
All service principal and workload federation activity is recorded in the C1 system log.Authentication events
Token operations are logged as OCSF Authentication events (class 3002). Theactivity_name corresponds to the OAuth grant type used.
Each authentication event includes:
- Outcome: Success or Failure
- Status detail: Specific failure reason (for example
trust_not_found,issuer_mismatch,invalid_jwt_format,cel_condition_not_met,token_too_old,sp_disabled) - Client IP: Source IP address of the request
- Client ID: The credential or trust client ID used
Failed token requests identify who made them:
- A failed client credentials request records its real failure reason in the status detail, along with the presented client ID and the owning service principal.
- A failed workload federation exchange records the trust, its provider, and the client ID that was presented.
- A token whose audience doesn’t match is recorded as
jwt_audience_mismatch.
API activity events
Service principal and workload federation CRUD operations are logged as OCSF API Activity events.
View these events in the system log.