Unexpected Error logging in to Enforce
search cancel

Unexpected Error logging in to Enforce

book

Article ID: 159998

calendar_today

Updated On:

Products

Data Loss Prevention Enforce

Issue/Introduction

Logging into Enforce produces an unexpected error:

100 SEVERE [com.vontu.model.data.validate.VarcharValidator] The parameter is too long.  Length cannot exceed 32 characters. arg=fe80:0:0:0:81e8:4b8a:6f12:cbf3%14

Cause:

java.lang.IllegalArgumentException: The parameter is too long.  The length cannot exceed 32 characters. arg=fe80:0:0:0:81e8:4b8a:6f12:cbf3%14

 

Resolution

Update the Apache Tomcat bind address within the server.xml file.

Location: \SymantecDLP\Protect\tomcat\conf\server.xml
Attribute Name: address
Syntax: address="0.0.0.0"

Example: Highlighted in yellow below

Connector SSLEnabled="true" URIEncoding="UTF-8" acceptCount="100"
ciphers="TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA"
clientAuth="false" debug="0" disableUploadTimeout="true" enableLookups="false"
keystoreFile="${CATALINA.EN_US}/conf/.keystore" keystorePass="protect"
maxSpareThreads="75" maxThreads="150"
address="0.0.0.0" port="443"
​scheme="https" secure="true"
sslEnabledProtocols="TLSv1.2" sslProtocol="TLS"
truststoreFile="${CATALINA.EN_US}/conf/truststore.jks" truststorePass="protect"/>

The value of 0.0.0.0 can also be set to a specific address in the special cases where the Enforce server has multiple IPv4 addresses/interfaces (multi-homed).

Alternatively, disabling IPv6 on the network interface will also force Tomcat to bind to an IPv4 address.