Base44: `getConnection()` Method and Enterprise SSO Authentication

Base44Mar 3, 2026

Base44 introduced two SDK-level improvements: a new getConnection() method for connectors that returns both an access token and service-specific configuration parameters, and SSO authentication support via auth.loginWithProvider('sso') for enterprise login flows. The original getAccessToken() method is now deprecated in favor of getConnection(), which handles connectors that require additional parameters like subdomains or account IDs. SSO must be enabled in the app authentication settings and is available on the Elite plan.

Sources & Mentions

1 external resource covering this update

Base44: Authentication just got a major upgrade — SSO and new login providers

X (Twitter)

SDK Updates: Smarter Connector Auth and Enterprise SSO

Base44 shipped two additions to its SDK: an improved method for accessing connector credentials, and a new authentication provider for enterprise single sign-on.

`getConnection()` Replaces `getAccessToken()`

The existing connectors.getAccessToken() method has been deprecated and replaced by connectors.getConnection(). The new method returns a ConnectorConnectionResponse object with two fields:

accessToken (string) — the OAuth token for the external service
connectionConfig (Record<string, string> | null) — connector-specific parameters required for API calls, such as subdomains, account IDs, or workspace identifiers. Returns null for services that do not require additional configuration.

This change addresses a practical limitation of the old method: some services require parameters beyond just a bearer token to construct valid API requests. For example, a Salesforce connector might return a subdomain in connectionConfig that is needed to form the correct API base URL. With getAccessToken(), developers had to handle this separately; getConnection() delivers everything in one call.

SSO Authentication Provider

The auth.loginWithProvider() method now accepts 'sso' as a valid provider value, alongside existing options like 'google', 'apple', and 'microsoft'. This enables enterprise login flows using an external identity provider (such as Okta or a company internal OIDC provider) instead of standard social authentication.

SSO must be configured first in the app authentication settings. Once enabled, calling auth.loginWithProvider('sso') initiates the SSO login flow. This feature is available on the Elite plan.

Why These Changes Matter

Both updates reflect Base44's growing focus on enterprise and developer-grade use cases. getConnection() makes it practical to work with services that have multi-tenant APIs or that require per-account configuration beyond a plain token. SSO support opens Base44-built apps to companies with strict identity management requirements — apps can now integrate with existing enterprise identity infrastructure rather than requiring users to create separate accounts.

Mentioned onX (Twitter)