You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
IdentityAssertion::validate doesn't resolve ingredient references or report hard_binding_incorrect #2847
SignerPayload::check_against_manifest, used by IdentityAssertion::validate / to_summary / summarize_from_reader, still checks references only against the manifest's own assertion_references(). It also only checks that some hard-binding reference exists.
What did you expect to happen?
Both validation paths apply the same §7.1 rules.
Notes
The two functions duplicate most of their logic. It may be simplest for check_against_manifest to build the same partial claim, including ingredient assertions, and delegate to check_against_partial_claim. Happy to send a PR once #2843 is reviewed.
Activity