June 2026 Summaries

Throughout June, enhancements have been made to improve user control and visibility, focusing on identity provider support, audit logging, and security measures. Notably, first-class support for Ping Identity has been introduced, allowing authentication via SAML or OIDC and user synchronization through SCIM without additional setup. The PropelAuth dashboard now includes features like leaving notes when resetting MFA, clearer indications of user lockouts, and IP blocking capabilities. Audit logs have been expanded to include detailed information on Enterprise SSO configurations and actions related to MCP Organization Scopes. Additionally, Enterprise SSO connections now require successful test runs before going live, and metadata.xml files can be uploaded to simplify SAML setup. Organization management has been improved with role-based filtering, and private IPs can now use HTTP in test environments to facilitate local development.

PropelAuth has expanded its support to include Ping Identity, a prominent identity provider critical for enterprise customers, by integrating SAML, OIDC, and SCIM standards. This allows B2B SaaS companies catering to regulated industries like finance and healthcare to easily meet security requirements. SAML is widely used for single sign-on, enabling users to log in with their work accounts, while OIDC offers a simpler authentication method based on OAuth 2.0. SCIM manages user data synchronization, automating provisioning and deprovisioning processes. The integration with Ping Identity is designed for self-service setup, eliminating the need for code changes and ensuring seamless operation of existing logic for organizations, roles, and permissions. PropelAuth also provides generic SAML and OIDC connections for compatibility with any standards-compliant identity provider, allowing customers to connect their IdP without requiring dedicated guides.

The PropelAuth Integration MCP server addresses the common issue of prolonged authentication setups and migrations by providing AI agents with tools to facilitate quick integration and migration from other auth providers like Clerk and Auth0. This server offers specific migration tools tailored for different parts of a tech stack, including frontend, backend, full-stack applications, and user data, detailing the steps and context needed for a seamless transition. The user and organizational data migration tool is particularly crucial, ensuring existing accounts are moved without disruption. The server is easy to set up, requiring no new installations for existing users, and allows migrations to be initiated through simple prompts. Users remain involved in the process, approving changes as they occur. While the current focus is on Clerk and Auth0 due to demand, feedback is encouraged for expanding support to other providers.

The article delves into the implementation of PropelAuth as a security layer for the Model Context Protocol (MCP) server, which connects large language models (LLMs) with sensitive organizational data, such as private repositories and databases. It highlights the potential risks of an unsecured MCP server, which could inadvertently grant excessive access to LLMs, leading to data breaches or unauthorized actions. PropelAuth addresses these issues by providing a robust authentication and authorization framework, including user management, role-based access control (RBAC), and Enterprise Single Sign-On (SSO) integrated with SCIM for automated user identity synchronization. This solution allows organizations to define specific roles and access scopes for their internal tools, effectively restricting data access based on departmental needs and preventing unauthorized actions. The article emphasizes the importance of securing AI infrastructure to harness the productivity benefits of MCP while maintaining stringent data protection measures.