[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wss4j-dev
Subject:    [jira] [Closed] (WSS-339) OCSP support
From:       "Colm O hEigeartaigh (JIRA)" <jira () apache ! org>
Date:       2014-10-07 8:05:36
Message-ID: JIRA.12542497.1329210665000.206397.1412669136026 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/WSS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Colm O hEigeartaigh closed WSS-339.
-----------------------------------

> OCSP support
> ------------
> 
> Key: WSS-339
> URL: https://issues.apache.org/jira/browse/WSS-339
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Freeman Fang
> Assignee: Colm O hEigeartaigh
> Attachments: WSS-339.patch
> 
> 
> currently WSS4J already support CRL for revocation check, it would be better that \
> we can also support OCSP through WSS4J configuration. Though we can set ocsp.enable \
> property in $JAVA_HOME/jre/lib/security/java.security to enable OCSP but it's \
> effect JVM wide, I'd like to introduce a property in WSHandlerConstants like \
> enableOCSP which can trigger code like Security.setProperty("ocsp.enable", \
> enableOCSP); This should be similar with the property enableRevocation,  the logic \
> is if (enableRevocation && enableOCSP) {
> //use OCSP to do revocation check.
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]