ValidSign
Getting started

Signing SBR Assurance does not work "certificate has not been found"

If you are unable to sign the SBR Assurance, please follow the steps below to verify that the configuration is correct:   Is ValidSign running in the backgroun

2 min readLast updated: 2021-10-14
If you are unable to sign the SBR Assurance, please follow the steps below to verify that the configuration is correct:
 
  1. Is ValidSign running in the background?
  2. Is the token / certificate correctly recognized?
Is ValidSign active?
 
Do you see the ValidSign icon at the bottom right of your taskbar (sometimes you just have to click on the arrow to show everything)?

 

vs2.png

If not, ValidSign is not active. Start up ValidSign (if you don't know how, ask the internal person responsible for the installation). Then start a new signature and try to sign again. If you are still unable to sign, follow the instructions below to verify that your token is recognized correctly.

Token recognition KPN certificate
 
Do you use a KPN certificate? Then do the following:
 
  • Open token management (you can find this between your applications)
  • Verify that the token status is operational (it may take a while to display this status):operationeel.png
  • Then check via Digital IDs> Show registered digital IDs whether 3 separate certificates are displayed and whether they are green:  


tokenbeheer.png

kpn.png

Token recognition QuoVadis certificate
 
Do you use a QuoVadis certificate? Then do the following:
 
  • Open the Safenet application (Safenet Authentication Tool)
  • Check if the certificate is recognized and active
  • If not, please contact us at support@validsign.nl

Was this article helpful?

Need help?

Contact our support team

Contact us