Environment
Novell Vibe Desktop client 2.0
Situation
Right after updating the Vibe Web Application certificate, the Vibe
Desktop client fails to connect and reports the following error in the vibe log:
2015-03-30 15:44:59,128 [server-monitor] [ERROR] Exception: <class 'pyasn1.error.PyAsn1Error'> (aca.excepts)
Traceback (most recent call last):
File "aca\onprem\apiserver.pyo", line 311, in IsServerAvailable
File "aca\onprem\apiserver.pyo", line 375, in RefreshServerVersion
....
....
File "aca\net\ssllib.pyo", line 513, in do_handshake
File "aca\net\ssllib.pyo", line 308, in raiseAppropriateException
PyAsn1Error: TagSet(Tag(tagClass=0, tagFormat=0, tagId=6), Tag(tagClass=128, tagFormat=32, tagId=0)) not in asn1Spec: GeneralName()
2015-03-30 15:44:59,131 [server-monitor] [INFO] Server status for account 1 (https://myvibe.domain.com): available=False; trusted=True; authorized=False (aca.apiserver)
2015-03-30 15:44:59,128 [server-monitor] [ERROR] Exception: <class 'pyasn1.error.PyAsn1Error'> (aca.excepts)
Traceback (most recent call last):
File "aca\onprem\apiserver.pyo", line 311, in IsServerAvailable
File "aca\onprem\apiserver.pyo", line 375, in RefreshServerVersion
....
....
File "aca\net\ssllib.pyo", line 513, in do_handshake
File "aca\net\ssllib.pyo", line 308, in raiseAppropriateException
PyAsn1Error: TagSet(Tag(tagClass=0, tagFormat=0, tagId=6), Tag(tagClass=128, tagFormat=32, tagId=0)) not in asn1Spec: GeneralName()
2015-03-30 15:44:59,131 [server-monitor] [INFO] Server status for account 1 (https://myvibe.domain.com): available=False; trusted=True; authorized=False (aca.apiserver)
Resolution
A fix for this issue is available in the Novell Vibe Desktop client 2.0 (June 1, 2015), available via the Novell Downloads.
With the fix in place, Vibe Desktop client will prompt the user to
accept the certificate which is not recognized as a valid certificate in
the Mozilla/FireFox CA.