Menu

signServer370: testing PDF signing - unable to get it working

Help
bostjans
2016-03-23
2016-04-02
  • bostjans

    bostjans - 2016-03-23

    Hi! Need some help/assistance at running SignServer.

    o1. Where is file
    According to documentation: doc/sample-configs/soft-crypto-configuration.properties
    --
    Setup the soft crypto token (if not already done) and activate it with its ID:
    $ bin/signserver setproperties doc/sample-configs/soft-crypto-configuration.properties
    --
    .. this file does not exists. Any idea where can I get this file? Do I need it?

    o2. PDF signing .. I can not get it working
    I tried to enable/test "Quick start demo PDF signer".
    So I set:
    --
    ./bin/signserver setproperties doc/sample-configs/keystore-crypto-configuration.properties
    ./bin/signserver setproperties doc/sample-configs/qs_pdfsigner_configuration.properties
    --

    But when I check the configuration, it reports:

    Current version of server is : SignServer CE 3.7.0

    The Global Configuration of Properties are :
    GLOB.WORKER2.CLASSPATH=org.signserver.module.pdfsigner.PDFSigner
    GLOB.WORKER1.SIGNERTOKEN.CLASSPATH=org.signserver.server.cryptotokens.KeystoreCryptoToken
    GLOB.WORKER1.CLASSPATH=org.signserver.server.signers.CryptoWorker
    The global configuration is in sync with the database.

    Status of CryptoWorker with id 1 (CryptoTokenP12) is:
    Worker status : Active
    Token status : Active
    Worker properties:
    KEYSTORETYPE=PKCS12
    CLASSPATH=org.signserver.common.ProcessableConfig
    DEFAULTKEY=Signer 2
    KEYSTOREPATH=/Users/bostjans/devel/Projekt/016_setcce.eKeeper/signserver-ce-3.7.0/res/test/dss10/dss10_signer2.p12
    KEYSTOREPASSWORD=foo123
    SIGNERCERT=
    NAME=CryptoTokenP12
    SIGNERCERTCHAIN=
    Authorized clients (serial number, issuer DN):

    Status of Signer with id 2 (PDFSigner) is:
    Worker status : Offline
    Token status : Active
    Signings : 0
    Errors:
    - No signer certificate available
    - No key available for purpose: null
    Worker properties:
    ADD_VISIBLE_SIGNATURE=True
    CRYPTOTOKEN=CryptoTokenP12
    DIGESTALGORITHM=SHA1
    LOCATION=Stockholm
    VISIBLE_SIGNATURE_CUSTOM_IMAGE_BASE64=iVB..ggg==
    REASON=Officially issued document
    VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH=C:\Dokumanlar\FOTO\Photos\15032009\100_3801.JPG
    SIGNERCERT=
    VISIBLE_SIGNATURE_PAGE=2
    AUTHTYPE=NOAUTH
    CLASSPATH=org.signserver.common.ProcessableConfig
    SIGNERCERTCHAIN=
    NAME=PDFSigner
    Authorized clients (serial number, issuer DN):
    Signer certificate:
    Error: No Signer Certificate have been uploaded to this signer.
    --
    Any idea? Please advice.

     
  • Markus Kilås

    Markus Kilås - 2016-04-02

    Hi bostjans,

    o1.
    It seems the documentation still refers to the old soft-crypto-configuration.properties that has now been removed. I have registered a ticket https://jira.primekey.se/browse/DSS-1171 to have the documentation updated.

    o2.
    You are doing the right thing when you instead use the keystore-crypto-configuration.properties.

    One thing missing in your configuration of the PDFSigner is to point out which key in the crypt token to use.
    You can set the worker property DEFAULTKEY for the PDFSigner and let it use the sample key "Signer 2" that exists in dss10_signer2.p12.

    Cheers,
    Markus
    PrimeKey Solutions

    Save time and money with an Enterprise support subscription. Please see www.primekey.se for more information.
    https://www.primekey.se/technologies/products-overview/
    https://www.primekey.se/service-support/support/

     

Log in to post a comment.