"Error verifying license: Invalid encoding for signature" still showing after upgrading license (4272091)

Converse agora com nosso suporte

Voltar

Feedback enviado

Este artigo resolveu um problema para você?

Selecione a classificação

Título

"Error verifying license: Invalid encoding for signature" still showing after upgrading license
Descrição

After upgrading the license per KB 225993 the application is still returning the following error message:
Exception in thread "main" com.dstc.security.util.licensing.InvalidLicense: Error verifying license: Invalid encoding for signature
Causa

The most likely cause for this issue is that there is still an old license being found in the application's CLASSPATH.
Resolução
To verify that there aren't any other old licenses inadvertently being applied remove the new license and make sure that you are seeing this message that indicates no license is found:
Exception in thread "main" com.dstc.security.util.licensing.InvalidLicense: Cannot load license for module idm.sso
(The module name may be different, e.g. "vsj.federation" rather than "idm.sso").
The most likely places that another old license may be found are:
1. In the jre/lib/ext directory of the JVM that you're using to execute the app server
2. In some directory that the app server provides for storing JAR files that may be used by any application. E.g. in Tomcat that is usually a directory like common/lib
Once all licenses have been removed take a screenshot showing the "Cannot load license" error then try adding back the new vsj-license.jar. If the "Invalid encoding for signature" error is still seen, then open a new case to look into the issue further.

Feedback enviado

Este artigo resolveu um problema para você?

Selecione a classificação

Conteúdo recomendado

Título