Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 13
Next »
Issue description | Detection | Fix | Workaround |
---|
The KeySign Connector is currently not installed in user space | - SigningHub returns an error saying the KeySign Connector is not installed
- https://vo-connector.keysign.eu/ returns an error saying the KeySign Connector is not installed
- Check if C:\Users\[end user]\AppData\Local\KeySignConnector directory is present
| Let the installer be run by the end user (download link in SigningHub error message)
|
|
The Sandbox service is not started | - SigningHub returns an error saying the KeySign Connector is not installed
- https://vo-connector.keysign.eu/ returns an error saying that the sandbox could not be contacted after 5 tries
| Install the new Middleware version 3.2.5 or higher |
|
A wrong version of the KeySign Connector has been installed | | Ask the user to install the latest KeySign Connector V3 version via the link in SigningHub or the link on https://vo-connector.keysign.eu/ |
|
Card not connected error | - SigningHub returns an error saying that the eID card is not connected.
- https://vo-connector.keysign.eu/ shows a message that the connector installed correctly but no cards and / or readers found
| - Verify the Belgian eID card is connected correctly to your computer.
- In case it is connected but still not detected verify the connector and card type.
|
|
Citrix / RDC/ Terminal server | The Client system is on an RDC / Citrix / Terminal environment | - Ask you Citrix/RDP/Terminal Server environment administrator to first install the KeySign Connector Proxy
- Users can then install the KeySign Connector as they normally would via the link in the pop-up in SigningHub
- In case users have already installed the KeySign connector before the proxy was installed they will have to re-install the connector
|
|
Reverse Proxy | If the Client system uses proxy, the KeySign Connector will not be recognized | Create an exception in your organisations proxy for : ksc.keysign.eu:52183 |
|