[WAL-1346] feat(wallet): configure proximity reader trust - #2167
[WAL-1346] feat(wallet): configure proximity reader trust#2167szijpeter wants to merge 4 commits into
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1a98938 to
d1d35e5
Compare
679ba35 to
091c7e8
Compare
|
|
Superseded by #2160 at |



Summary
Closed as superseded — do not merge standalone. Its complete four-commit delta was transplanted into #2160 with 4/4 exact patch-equivalence proof. The Settings/public-file-import work also lands only in #2160.
Completes the application-configurable holder-side reader-trust policy for WAL-1346. Applications can now supply explicit Reader CA anchors, revocation policy, and optional RICAL providers through one immutable Kotlin/Swift configuration; the SDK still ships no universal trust list and never promotes reader-supplied certificates to trust anchors.
This PR is stacked on the three-demo proximity journey in walt-id/waltid-identity#2160. The governing architecture and trust boundary are documented in walt-id/waltid-architecture#60.
What Changed
Shared X.509 and RICAL validation
Wallet SDK configuration
Contract and UI alignment
Architecture Notes
Caveats and Follow-Ups
Breaking
No released API is broken. The mobile SDK is still unpublished, so the new trust configuration and exhaustive result state are introduced without migration aliases or compatibility shims.