nobo

Hello again, I've managed to sign with curl : curl -F workerName=CMSSignerClientSide -F file=@pre-computed-hash.bin --output test.sig -F REQUEST_METADATA.USING_CLIENTSUPPLIED_HASH=true -F REQUEST_METADATA.CLIENTSIDE_HASHDIGESTALGORITHM=SHA-256 http://SignServer:9006/signserver/process The metadata parameters are REQUEST_METADATA.USING_CLIENTSUPPLIED_HASH and REQUEST_METADATA.CLIENTSIDE_HASHDIGESTALGORITHM. I had to capture traffic of signclient request to find out about the name of the metadata attributes...

Hello again, I've managed to sign with curl : curl -F workerName=CMSSignerClientSide -F file=@pre-computed-hash.bin --output test.sig -F REQUEST_METADATA.USING_CLIENTSUPPLIED_HASH=true -F REQUEST_METADATA.CLIENTSIDE_HASHDIGESTALGORITHM=SHA-256 http://SignServer:9006/signserver/process The metadata parameters are REQUEST_METADATA.USING_CLIENTSUPPLIED_HASH and REQUEST_METADATA.CLIENTSIDE_HASHDIGESTALGORITHM. I had to capture traffic of signclient request to find out about the name of the metadata attributes....

Alright, thank you very much. What about signing remotely with a CURL for example ? Does this work ? Are these the right metadata parameters? curl -F USING_CLIENTSUPPLIED_HASH=true -F CLIENTSIDE_HASHDIGESTALGORITHM=SHA-256 ... Cheers, Noboa.

Hello, I'm trying to set Client Side CMSSigner worker, and to be completely honest I'm not 100 % sure of what I'm doing. So I have the following configuration file : # Sample configuration of a CMSSigner. # ## General properties WORKERGENID1.TYPE=PROCESSABLE WORKERGENID1.IMPLEMENTATION_CLASS=org.signserver.module.cmssigner.CMSSigner WORKERGENID1.NAME=CMSSignerClientSide WORKERGENID1.AUTHTYPE=NOAUTH # Crypto token WORKERGENID1.CRYPTOTOKEN=CryptoTokenP12 #WORKERGENID1.CRYPTOTOKEN=CryptoTokenP11 #WORKERGENID1.CRYPTOTOKEN=CryptoTokenP11NG1...

Hello, I'm trying to set Client Side CMSSigner worker, and to be completely honest I'm not 100 % sure of what I'm doing. So I have the following configuration file : # Sample configuration of a CMSSigner. # ## General properties WORKERGENID1.TYPE=PROCESSABLE WORKERGENID1.IMPLEMENTATION_CLASS=org.signserver.module.cmssigner.CMSSigner WORKERGENID1.NAME=CMSSignerClientSide WORKERGENID1.AUTHTYPE=NOAUTH # Crypto token WORKERGENID1.CRYPTOTOKEN=CryptoTokenP12 #WORKERGENID1.CRYPTOTOKEN=CryptoTokenP11 #WORKERGENID1.CRYPTOTOKEN=CryptoTokenP11NG1...

Hello, I'm trying to set Client Side CMSSigner worker, and to be completely honest I'm not 100 % sure of what I'm doing. So I have the following configuration file : # Sample configuration of a CMSSigner. # ## General properties WORKERGENID1.TYPE=PROCESSABLE WORKERGENID1.IMPLEMENTATION_CLASS=org.signserver.module.cmssigner.CMSSigner WORKERGENID1.NAME=CMSSignerClientSide WORKERGENID1.AUTHTYPE=NOAUTH # Crypto token WORKERGENID1.CRYPTOTOKEN=CryptoTokenP12 #WORKERGENID1.CRYPTOTOKEN=CryptoTokenP11 #WORKERGENID1.CRYPTOTOKEN=CryptoTokenP11NG1...

Hello, I'm trying to set Client Side CMSSigner worker, and to be completely honest I'm not 100 % sure of what I'm doing. So I have the following configuration file : # Sample configuration of a CMSSigner. # ## General properties WORKERGENID1.TYPE=PROCESSABLE WORKERGENID1.IMPLEMENTATION_CLASS=org.signserver.module.cmssigner.CMSSigner WORKERGENID1.NAME=CMSSignerClientSide WORKERGENID1.AUTHTYPE=NOAUTH # Crypto token WORKERGENID1.CRYPTOTOKEN=CryptoTokenP12 #WORKERGENID1.CRYPTOTOKEN=CryptoTokenP11 #WORKERGENID1.CRYPTOTOKEN=CryptoTokenP11NG1...

Thank you for the help. I was to able to sign a pdf and protected pdf.