|
From: Tomas G. <to...@pr...> - 2018-03-04 15:50:15
|
Hm, sounds more that it's something with the script. Using a password longer than 250 characters sounds really excessive to me. What in the script generates such a long password?
When does the error occur?
Do you use the script provided with EJBCA, or some external version?
Regards,
Tomas
On March 4, 2018 11:53:04 AM GMT+01:00, Christian Felsing via Ejbca-develop <ejb...@li...> wrote:
>Hello,
>
>while testing ejbca-setup with 6.10.1.2 following problem occurs while
>install process:
>
>Data too long for column 'clearPassword' at row 1
>
>which is caused by a SQL declaration for clearPassword with a length of
>250. Wildfly log shows a real length of 517. For now a very nasty hack
>in ejbca-setup fixes that:
>
>doPatch() {
> if [ $EJBCA_RELEASE == "6_10_1_2" ]; then
> cd ejbca || exit 1
> sed -i.bak 's/<basic fetch="EAGER" name="clearPassword"><column
>name="clearPassword" column-definition="VARCHAR(250)
>BINARY"\/><\/basic>/<basic fetch="EAGER" name="clearPassword"><column
>name="clearPassword" column-definition="VARCHAR(1000)
>BINARY"\/><\/basic>/g' modules/ejbca-entity/resources/orm-ejbca-
>mysql.xml || exit 1
> echo "patch for 6_10_1_2 applied"
> cd ..
> fi
>}
>
>
>Christian
>
>------------------------------------------------------------------------------
>Check out the vibrant tech community on one of the world's most
>engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>_______________________________________________
>Ejbca-develop mailing list
>Ejb...@li...
>https://lists.sourceforge.net/lists/listinfo/ejbca-develop
|