Embedded Configuration
Reference to a signed configuration bundled with the app, used by TrustPinConfiguration.embeddedConfiguration as a last-resort fallback when no online source and no previously fetched configuration is available — typically an app's very first start during an outage.
Use it only in applications protected by runtime application self-protection (RASP) that guards the app's bundled resources against modification. Without such protection, do not set it.
The referenced file must be the unmodified signed payload downloaded from the TrustPin dashboard for this project. It is verified against TrustPinConfiguration.publicKey at TrustPin.setup; the file should be regenerated by your build pipeline on every release so it is never older than the app that ships it. Pins in an old file expire on their own schedule — an embedded configuration whose pins have all expired is equivalent to no fallback.
Inheritors
Types
A bundled resource addressed by name.
A regular file on the JVM, resolved relative to the working directory when not absolute. Must live inside the application's own installation (the working directory or a class-path root); anything else is rejected at TrustPin.setup. Not supported on Android — use Asset.