How do Okta or Auth0 fit alongside workload identity for agents?

Okta, Auth0, and similar identity providers are useful for human user authentication and enterprise access management. Workload identity solves a different problem: identifying software components such as agents, services, and tools. In agent systems, both may be needed. A user may initiate a task through an enterprise identity provider, while the agent and MCP server still need their own workload identities for service-to-service calls. Teams should connect human identity, agent identity, and tool policy rather than replacing one with the other. Diagrid's zero-trust model focuses on this production workload identity layer.