Anthropic introduces a built-in identity assertion capability in Claude, allowing companies to automatically connect employees to approved plugins without repeated manual sign-ins. This innovation works even with limited identity provider support for enterprise authorization extensions, streamlining workflows and enhancing security.
- Automatic plugin connections reduce repetitive user sign-ins
- Claude issues signed identity assertions, easing identity provider dependency
- Administrators control access by service and employee role
Infrastructure signal
Anthropic’s new capability embeds identity issuance within Claude for plugin authentication, marking a shift in cloud infrastructure by reducing reliance on external identity provider extensions. This reduces friction in secure application access and can decrease cloud overhead related to managing multiple token exchanges and failed authentications.
The approach broadens compatibility across enterprise ecosystems, especially where identity providers have yet to adopt the Enterprise-Managed Authorization (EMA) extensions to the Model Context Protocol (MCP). By internally issuing signed assertions, Claude acts as an identity broker, simplifying the integration surface and potentially improving overall system reliability by cutting down external dependency points.
Developer impact
Developers building plugins for Claude now have the option to implement support for receiving Claude-issued identity assertions, enabling smoother onboarding and fewer authentication interruptions for users. This reduces developer effort needed to handle diverse identity provider capabilities and token refresh workflows.
This feature enhances the developer workflow by enabling a centralized authorization model within Claude, accelerating time to value for plugin integration while preserving security best practices. Developers can expect fewer support cases related to authentication errors and can focus more on core plugin functionality and user experience.
What teams should watch
Cloud infrastructure and security teams should assess how automatic identity assertions impact their access control policies, especially in balancing ease of use with data protection. The ability to assign plugin access by role provides granular control, necessitating close coordination with HR and compliance stakeholders to ensure proper role assignments and auditability.
Operations teams need to monitor token issuance flows and assertion validation closely since Claude now plays a critical role in the authentication chain. Observability tools should be adapted to track assertion usage patterns and failures. Additionally, teams should watch for the adoption of EMA support among identity providers to evaluate when native integrations might replace the need for Claude-based identity assertions.