Re: [Engine-devel] BadPaddingException
----- Original Message -----
From: "Alon Bar-Lev" <alonbl(a)redhat.com>
To: "Martin Perina" <mperina(a)redhat.com>
Cc: engine-devel(a)ovirt.org
Sent: Monday, July 8, 2013 2:01:56 PM
Subject: Re: [Engine-devel] BadPaddingException
----- Original Message -----
> From: "Martin Perina" <mperina(a)redhat.com>
> To: engine-devel(a)ovirt.org
> Sent: Monday, July 8, 2013 2:58:08 PM
> Subject: [Engine-devel] BadPaddingException
>
> Hi,
>
> I've noticed that BadPaddingException has started to appear recently in
> engine-log:
>
> 1) The first occurrence is during engine startup:
>
> 2013-07-08 13:42:32,334 ERROR
> [org.ovirt.engine.core.dal.dbbroker.generic.DBConfigUtils] (MSC service
> thread 1-4) Failed to decrypt value for property
> AttestationTruststorePass will be used encrypted value:
> javax.crypto.BadPaddingException: Data must start with zero
>
>
> 2) The second occurrence is after successfull login to webadmin app
>
> 2013-07-08 13:43:13,352 ERROR
> [org.ovirt.engine.core.dal.dbbroker.generic.DBConfigUtils]
> (http--0.0.0.0-8080-1) Failed to decrypt value for property
> LocalAdminPassword will be used encrypted value:
> javax.crypto.BadPaddingException: Data must start with zero
>
>
> Strange thing is, that I can log in as admin@internal without any problems
> with the password I've entered
> during engine-setup-2 process.
>
> Engine instance has been created using new development environment with no
> errors, engine.log attached.
Right.
This was always the case, the only change is that I added a stack trace for
these errors.
Now someone need to figure out why we would like to decrypt the default
password of 123456 if I recall correctly, and fix this... :)
Maybe because Engine first assumes the password is encrypted and tries to decrypt it,
otherwise it just uses the immediate value.
Alon
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel