Map Okta System Log events to DAT trust signals. Query trust scores for policy decisions. Bridge enterprise IAM with behavioral trust—so your identity provider knows not just who an agent is, but how it behaves.
Nine Okta System Log event types automatically mapped to DAT's behavioral trust model.
Every time an agent authenticates through Okta—successful MFA, failed sign-on, account lockout, threat detection—DAT captures that event and converts it into a weighted trust signal. No manual mapping. No custom code. Connect your Okta Event Hook and trust scores update in real time.
Every signal carries full Okta attribution: event type, event ID, severity, outcome, and actor display name. Your audit trail traces every trust change back to the exact Okta event that caused it.
Okta Event -> DAT Signal Mapping
==============================
Okta Event | DAT Signal
---------------------|----------
user.session.start | success
auth_via_mfa | success
sso | success
sign_on.fail | failure
token.revoke | failure
account.lock | violation
unauth_app_access | violation
threat.detected | fraud
lifecycle.deactivate | blocked
Signal Metadata:
{
source: "third_party",
integration: "okta",
oktaEventType: "user.session.start",
oktaEventId: "tev123abc",
oktaSeverity: "INFO",
oktaOutcome: "SUCCESS",
actorDisplayName: "Agent-7B",
pillar: "reliability",
timestamp: "2026-03-04T..."
}Query DAT trust scores from your Okta workflows to make smarter access control decisions.
Okta tells you who an agent is. DAT tells you whether to trust it right now. Query the trust API from your Okta policies to get tier-based recommendations that translate behavioral trust into actionable access decisions—from full access to complete denial.
Batch queries support up to 100 DIDs in a single request, and Redis-cached DID mappings ensure sub-millisecond lookups from Okta actor IDs to DAT agent identities.
Trust Query API
==============================
GET /gateway/okta/trust/:agentDid
Response:
{
"trustScore": 82.4,
"tier": "allow_with_monitoring",
"recommendation": "monitor",
"pillars": {
"reliability": 85,
"performance": 78,
"compliance": 90,
"security": 72,
"reportingFidelity": 80
}
}
Batch Query (up to 100 DIDs):
POST /gateway/okta/trust/batch
{
"agentDids": [
"did:dat:testnet:agent_abc",
"did:dat:testnet:agent_def",
...
]
}
DID Mapping (Redis):
Okta Actor ID <-> DAT Agent DID
Bidirectional lookup
Sub-millisecond resolutionThe full pipeline has been verified on a live Okta tenant—from login event to on-chain reputation.
This is not a demo. A real Okta tenant with a verified Event Hook feeds live authentication events into DAT's trust pipeline. The result: a user logs into Okta, DAT records the trust signal, recalculates the agent's score, and the ERC-8004 bridge syncs the updated reputation to the Sepolia blockchain.
For enterprises, this means your Okta investment becomes more valuable. Authentication events that were previously just audit logs now actively shape your agents' capabilities and on-chain identity.
Live Pipeline (Verified)
==============================
1. User logs into Okta
Event: user.session.start
Outcome: SUCCESS
2. Okta Event Hook fires
POST /gateway/okta/hooks/events
Authorization: Bearer {secret}
3. Gateway resolves actor DID
Redis: dat:okta:mapping:{id}
-> did:dat:testnet:agent_abc
4. Signal forwarded to reputation
POST /api/v1/reputation/signal
Type: action_success
Source: third_party
Description: "Okta:
user.session.start (SUCCESS)"
5. Trust score recalculated
Score: 55.0 -> 59.42
6. ERC-8004 bridge detects change
delta >= 5 -> sync triggered
7. Sepolia transaction mined
tx: 0xd1d52310...
Score on-chain: 5942 (uint256)
Total time: < 5 minutesYour identity provider already knows who your agents are. Now give it the intelligence to know how much to trust them.