Skip to main content
The IDP SDK is built around an isolated-host auth model. That boundary is the main reason to use the SDK instead of assembling the flow yourself.

​
What the app receives

After a successful callback, the SDK persists a Swig session with:
  • configAddress
  • walletAddress
  • roleId
  • authFlow
  • updatedAt
The app receives session data. It does not receive the OAuth or OTP internals that were handled inside the isolated host.

​
Where sensitive steps happen

Sensitive auth steps stay inside the isolated host:
  • OAuth redirects
  • email or phone entry
  • OTP verification
  • callback JWT handling
That is why the supported mobile flow uses a system auth session instead of an embedded WebView.

​
Default storage by platform

Both paths let you override storage if your app needs a custom adapter.

​
Backend assumptions

By default, the SDK expects Swig identity and wallet endpoints behind the configured backend base URL and isolated-host URL. The default backend routes include:
  • /identity/public/auth/start
  • /identity/public/auth/email/start
  • /identity/public/auth/sms/start
  • /identity/public/auth/email/verify
  • /identity/public/auth/sms/verify
  • /identity/public/callback/{provider}
The published swig-idp-sdk endpoint defaults still use the retired /identity/api/* paths. Its current endpoint configuration type also does not fully model the public OTP and setup routes above, so a simple endpoint override is not a complete compatibility fix. Use the current backend route contract deliberately until the IDP SDK is refreshed.

​
Configuration points

The main config levers are:
  • baseUrl
  • isolatedHostUrl
  • redirectUri
  • network
  • storage
  • storageKey
  • endpoints
Use these when you need non-default backend URLs, custom storage, or a different network.