Quick start
A 5-minute path for developers adopting Modfolio Connect for the first time.
Like “Sign in with Google”, but for these services. Sign up once and the same account opens every service that supports Connect.
How it worksDifferent brands, different screens. Only the sign-in is shared — and the list is growing.
See allReal situations instead of jargon. Six separate layers each guard the account.
See the six layersRegister an app and switch sign-in on with one line of SDK. Schools and companies, talk to us.
Developer guideModfolio Connect does not invent its own protocols. Every behavior complies with the open standards of IETF · OASIS · OpenID · W3C. This page is an entry hub gathering each standard's spec source + our SDK's mapping.
A 5-minute path for developers adopting Modfolio Connect for the first time.
Standards compliance for PKCE · PAR · DPoP · token introspection · back-channel logout, and more.
L3 + PRF extension + Conditional UI. device-bound vs synced passkey classification.
Chrome FedCM API · Active Mode · IdP sign-in status. A standards-based alternative to third-party cookies.
OpenID Shared Signals Framework v1.0. Real-time propagation of session revocation / credential change.
Enterprise federation. SAML 2.0 SP assertion + SCIM 2.0 automatic provisioning.
@modfolio/connect-sdk/agent · delegation chain · per-agent depth limit.
Disaster Recovery · OTLP tracing · secret redaction · WAF rate limit.