[ 
https://issues.apache.org/jira/browse/RAMPART-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678165#comment-16678165
 ] 

Svetoslav ILIEV edited comment on RAMPART-445 at 11/7/18 12:44 PM:
-------------------------------------------------------------------

Hi Andreas Veithen,

 

Thanks for your quick response!

I am curious about AOP solution introduced in version 1.7.x revisions r1837550 
and r1837559.

Why the byte code manipulation via Aspects was preferred as solution instead of 
regenerating expired certificates?

What is the intention here?

 

Warm Regards,

Svetoslav ILIEV

 


was (Author: slaviliev):
Hi Andreas,

 

Thanks for your quick response!

I am curious about AOP solution introduced in version 1.7.x revisions r1837550 
and r1837559.

Why the byte code manipulation via Aspects was preferred as solution instead of 
regenerating expired certificates?

What is the intention here?

 

Warm Regards,

Svetoslav ILIEV

 

> Expired certificates in rampart project
> ---------------------------------------
>
>                 Key: RAMPART-445
>                 URL: https://issues.apache.org/jira/browse/RAMPART-445
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-integration
>    Affects Versions: 1.6.2
>            Reporter: Svetoslav ILIEV
>            Priority: Major
>             Fix For: 1.7.2
>
>
> We observed expired certificates in Apache Rampart project. Keystores with 
> expired certificates are located in:
> <rampart_root>\modules\rampart-integration\src\test\resources\rahas\rahas-sts.jks
>  
> and 
> <rampart_root>\modules\rampart-integration\src\test\resources\rahas\sec.jks
> Other Rampart versions might be also affected.
> Could you please renew the expired certificates?
>  
> Best Regards,
> Svetoslav ILIEV



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to