1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
/*
* Copyright Nitro Agility S.r.l.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* https://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
//! Proof of Relationship validation boundary.
//!
//! `proof_of_relationship` is a typed container: `type` selects how
//! `evidence` is parsed and validated, and the selected schema must bind or
//! identify the workload verification key used to verify the three
//! workload-signed candidate artifacts.
//!
//! Current Profile 0.2 requires `type = "sd-jwt"` with the exact UTF-8 bytes
//! of the textual issuer-signed SD-JWT presentation as evidence. This crate
//! does **not** ship an SD-JWT (RFC 9901) implementation yet: deployments
//! plug their SD-JWT stack (issuer trust, disclosure processing, key
//! extraction) through [`PorValidator`]. PoR evidence supports the accepted
//! relationship; it is not, by itself, Proof of Continuity — the Verifier
//! still performs every other required check.
use crateProofOfRelationship;
use crateRejectReason;
use crateArtifactVerifier;
/// Validates PoR evidence and yields the accepted workload verifier.