English 
Tiếng ViệtApplication selects provider and service
JCA/JCE provider registration
JCA · PROVIDER / SDK PROFILE
Trusted PQC Java JCA/JCE Provider
Controlled pilot
Support Java 21 application integration for keys, signatures, CMS and trust-service workflows.
CUSTOMER PROBLEM
Support Java 21 application integration for keys, signatures, CMS and trust-service workflows.
Java applications need provider-level PQC integration that works with keystores, CMS, Jakarta EE and approved library combinations.
Controlled pilot
- Portfolio class
- Provider / SDK profile
- Public profile
- 2026.07
- Version rule
- Confirmed in quotation / release record
PRODUCT-SPECIFIC IMPLEMENTATION FLOW
How Trusted PQC Java JCA/JCE Provider operates from input to evidence.
Java 17/21, WildFly/Jakarta EE and approved library combinations. Provider tests, JDK matrix, sample code, signed artifacts and known-limitations register.
JCA resolves algorithm implementation
KeyPairGenerator, Signature and KeyFactory profiles
Provider validates parameters and key type
KeyStore and token integration
KeyStore or HSM supplies protected key
CMS/CAdES sample workflows
Signature/CMS workflow creates artifact
Java 17/21 and WildFly/Jakarta EE profiles
Verifier records provider and JDK manifest
Provider-order and compatibility diagnostics
NAMED COMPONENTS AND RESPONSIBILITIES
What Trusted PQC Java JCA/JCE Provider contains and what each component does.
The descriptions below state concrete technical behaviour rather than generic support language.
JCA/JCE provider registration
Registers provider name, priority and services so Java applications can select Mobile-ID implementations explicitly or through policy-controlled provider order.
KeyPairGenerator, Signature and KeyFactory profiles
Implements KeyPairGenerator, Signature and KeyFactory service profiles with approved names, aliases, parameter validation and deterministic error behavior.
KeyStore and token integration
Connects Java KeyStore entries to software, token or HSM keys while preserving aliases, certificate chains and non-exportability rules.
CMS/CAdES sample workflows
Provides CMS/CAdES examples that identify the signing profile, digest, attributes, certificate path and verifier needed to reproduce the result.
Java 17/21 and WildFly/Jakarta EE profiles
Tests Java 17/21, WildFly modules, Jakarta EE class loading, provider isolation and application-server lifecycle with exact build manifests.
Provider-order and compatibility diagnostics
Reports provider-order conflicts, unsupported key classes, native-library loading and verifier incompatibilities with actionable diagnostics.
- JCA/JCE integration
- CMS and signing samples
- Jakarta EE deployment profile
Java 17/21, WildFly/Jakarta EE and approved library combinations.
Developer sandbox
A pinned provider/SDK build, sample application, test key backend and diagnostics are supplied for repeatable integration.
Application pilot
One named application and runtime are integrated with exact algorithms, key backend, test corpus and rollback.
Enterprise release channel
Signed packages, compatibility matrix, upgrade policy, monitoring and support ownership govern broader rollout.
- Provider tests, JDK matrix, sample code, signed artifacts and known-limitations register.
- Version and configuration manifest for: Java 17/21, WildFly/Jakarta EE and approved library combinations.
- Negative, failure and recovery tests for “Signature/CMS workflow creates artifact” and “Verifier records provider and JDK manifest”.
- Signed acceptance record, accountable owner, published limitations and next review date.
STANDARDS & PROFILES
- Java JCA/JCE
- Java 17/21
- CMS / CAdES
- Jakarta EE / WildFly
PRODUCT-SPECIFIC BOUNDARIES
Conditions that must remain true for Trusted PQC Java JCA/JCE Provider.
These points come from the product profile, not from a shared disclaimer.
NEXT STEP
Define a controlled pilot: Trusted PQC Java JCA/JCE Provider
Select one application, exact versions, measurable acceptance criteria and rollback.