According to Section 4.1, "Wallet-Centric Model" in CS-03
The Wallet Unit acts as both credential holder and Signature Creation Application, producing AdES signatures locally.
Why is it required that the signature is created locally? Why does the specification not allow the wallet to use remote SCA and QSCD? It seems to me that, at least from the scope of this document, "Wallet centric" vs "Server centric" is about the RP requesting a signature from the WU or QTSP.
In pull-request #298 I allow the wallet to use external or remote SCA in the alternative signature request protocol.
I propose that we allow the wallet to use external and remote SCA in the QTSP centric model.
Update 2026-08-28 This issue is related to use case WP3, PA3 (Business bank account opening) Scenario 2 (Digital signature). The use case assumes that the signature creation application is at the bank portal. That aspect does not appear to be supported by the current version of CS-03.
According to Section 4.1, "Wallet-Centric Model" in CS-03
Why is it required that the signature is created locally? Why does the specification not allow the wallet to use remote SCA and QSCD? It seems to me that, at least from the scope of this document, "Wallet centric" vs "Server centric" is about the RP requesting a signature from the WU or QTSP.
In pull-request #298 I allow the wallet to use external or remote SCA in the alternative signature request protocol.
I propose that we allow the wallet to use external and remote SCA in the QTSP centric model.
Update 2026-08-28 This issue is related to use case WP3, PA3 (Business bank account opening) Scenario 2 (Digital signature). The use case assumes that the signature creation application is at the bank portal. That aspect does not appear to be supported by the current version of CS-03.