Re: [Ejbca-develop] CertificateDataBean doubts

[Ejbca S. <ejb...@pr...>]

I think we should remove the TEMP_REVOKED constant. It is of no use.

/Tomas

EJBCA Support wrote:
> I'm not sure about the temp_revoked constant, Tomas have to come back t=
o=20
> you about this since it's he that defined the constant once :)
>=20
> But another thing I have thought about is that is should also be=20
> possible to change the revoke reason of a certificate with certificate=20
> hold. It not very convenient to be forced to first unrevoke before=20
> revoking it with another reason.
>=20
> Regards
> Philip
>=20
> Javier Aparicio Conesa wrote:
>=20
>> Hi,
>> I'm again...
>>
>> I can see in CertificateDataBean some state constants defined. Are all=
=20
>> in use?
>>
>>     /** Certificate is temporarily blocked (reversible) */
>>     public static final int CERT_TEMP_REVOKED =3D 30;
>>
>> CERT_TEMP_REVOKED is must be related with the revocation reason=20
>> CERTIFICATE HOLD?
>>
>> When i try to reactivate a certificate... i'm checking his state in=20
>> this way before reactivate it:
>>
>> if (rev.getStatus() =3D=3D CertificateDataBean.CERT_REVOKED) {
>>     rev.setStatus(CertificateDataBean.CERT_ACTIVE);
>>     rev.setRevocationDate(null);
>>     rev.setRevocationReason(RevokedCertInfo.NOT_REVOKED);
>> }
>>
>> Does I must change the if clause to check CERT_TEMP_REVOKED?
>>
>> And the last question, to reactivate a certificate is enough with the=20
>> operations declared in the if block?
>>
>> Thanks in advance,
>> Javier
>>
>> --=20
>>
>> Autoridad de Certificaci=F3n de la Comunidad Valenciana=20
>> <http://www.accv.es>
>>
>>       *Javier Aparicio*
>>
>>       c/Col=F3n, 66 1=AA Planta - 46004 Valencia
>>
>>       jap...@ac... <mailto:jap...@ac...>
>>
>>       Tel: 961961168
>>
>=20
>=20