Expand description
Immutable security policy snapshots shared by XML Security operations.
Policy contains trusted, reusable decisions. Caller-owned keys, selected document targets, tenant identity, and external resource bytes remain in operation request contexts and are deliberately not stored here.
Structs§
- Compiled
Policies - Immutable compiled output. Operation snapshots retain all constraints and authorization metadata when cloned into existing processing contexts.
- Decryption
Policy - Immutable policy snapshot for XMLEnc decryption.
- DsaKey
Policy - DSA strength requirements for legacy signature verification.
- Encryption
Policy - Immutable policy snapshot for XMLEnc encryption.
- Hmac
Policy - HMAC key-strength and truncation requirements shared by signing and verification.
- KeyEstablishment
Policy - Immutable permission and limits shared by encryption and decryption.
- KeySource
Policy - KeyInfo sources an XMLDSig verification operation is permitted to trust.
- KeyTrust
Policy - X.509 and key-resolution decisions for verification.
- Policy
Compile Context - Caller-owned capabilities promised to operations using the compiled policy. This is a contract, not permission to discover resources. Actual resource maps and target identities must still be supplied to each operation.
- Policy
Compiler - Compose layers in system → application → tenant order. Every ordinary layer
intersects the previous snapshot; only
authorize_replacementcan relax it. - Policy
Set - Editable compilation input.
Nonedisables an operation; a restrictive layer can disable but never re-enable an operation inherited as disabled. - Policy
Validity - Auditable, caller-authorized exception with an exclusive expiration boundary. The core does not decide who is entitled to grant exceptions; the trusted application authenticates that authority before constructing this value.
- Resource
Policy - Resource ceilings shared by parsing, transforms, and cryptographic output.
- RsaKey
Policy - RSA strength and structural requirements for cryptographic operations.
- Signing
Policy - Immutable policy snapshot for XMLDSig signing.
- Transform
Policy - XMLDSig transform and canonicalization decisions shared by signing and verification.
- UriPolicy
- URI-class decisions shared by XMLDSig reference and key retrieval processing.
- Verification
Policy - Immutable policy snapshot for XMLDSig verification.
- XmlInput
Policy - XML parsing decisions shared by all operation policies.
Enums§
- Certificate
Signature Algorithms - Explicit certificate/CRL permissions, independent of XML signature methods.
- Ecdsa
Signature Value Encoding - Wire representation used for ECDSA
SignatureValuebytes. - Extended
KeyPurpose - An RFC 5280 extended-key-purpose identifier accepted for XML signing.
- KemContent
Authentication - Authentication boundary for content encrypted directly with a KEM secret.
- KeyAgreement
Algorithm - Agreement mechanisms identified by their XML algorithm URI.
- KeyDerivation
Algorithm - KDF mechanisms accepted by the shared policy domain.
- Manifest
Processing - Whether an XMLDSig operation evaluates Manifest references. Verification requires original authenticated coverage; signing populates direct Object/Manifest digests.
- OpcRelationship
Edition - Trusted edition of relationship selection and normalization. This is not an OPC package-conformance profile: signature placement and package-wide part identity constraints require a package validator.
- Policy
Profile - XML Security presets, selected only by trusted application code. These names do not certify full SAML, SOAP or XAdES conformance.
- Policy
Violation - A typed rejection produced by an operation policy.
- RsaPss
Permission - Permission for the unbounded parameterized RSA-PSS family. Exact permissions continue to use the signature algorithm allowlist.
- Same
Document IdSemantics - XMLDSig transform and canonicalization decisions shared by signing and verification.
- Signature
Constraints - Signature-level XML Security constraints, not application protocol semantics.
- Verification
Trust Mode - Whether verification must establish signer authorization in addition to mathematics.