Ditto Identity
The various identity configurations that you can use when initializing a Ditto instance.
Phased out in 4.x — superseded by DittoConfig for initialization. The new configuration-based design enables a more extensible and maintainable setup. This API will be replaced by DittoConfig in v5.
Migration guide:
OfflinePlayground → DittoConfigConnect.SmallPeersOnly with no private key
OnlinePlayground → DittoConfigConnect.Server with DittoAuthenticationExpirationHandler
OnlineWithAuthentication → DittoConfigConnect.Server with DittoAuthenticationExpirationHandler
SharedKey → DittoConfigConnect.SmallPeersOnly with private key
Manual → Not supported by DittoConfigConnect
Inheritors
Types
A manually-provided certificate identity. This accepts a base64-encoded bundle.
Develop peer-to-peer apps with no cloud connection. This mode offers no security and must only be used for development. In this mode, any string can be used as the name of the app.
Test a Ditto Cloud app with weak shared token authentication ("Playground mode"). This mode is not secure and must only be used for development.
Run Ditto in secure production mode, logging on to Ditto Cloud or on on-premises authentication server. User permissions are centrally managed. Sync will not work until a successful login has occurred.
A mode where any device is trusted provided they know the secret key. This is a simplistic authentication model normally only suitable for private apps where users and devices are both trusted. In this mode, any string may be used as the app id.