You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Ioan Eugen Stan (JIRA)" <se...@james.apache.org> on 2013/02/28 10:49:13 UTC
[jira] [Closed] (JAMES-370) RFE: Add client certificate-based
authentication
[ https://issues.apache.org/jira/browse/JAMES-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ioan Eugen Stan closed JAMES-370.
---------------------------------
Resolution: Unresolved
Assignee: Ioan Eugen Stan
Too old. No longer relevant.
> RFE: Add client certificate-based authentication
> ------------------------------------------------
>
> Key: JAMES-370
> URL: https://issues.apache.org/jira/browse/JAMES-370
> Project: James Server
> Issue Type: New Feature
> Components: James Core
> Affects Versions: 2.3.0
> Environment: any
> Reporter: Ralf Hauser
> Assignee: Ioan Eugen Stan
>
> org.apache.coyote.http11.Http11Processor.action() with its ActionCode.ACTION_REQ_SSL_CERTIFICATE or rather org.apache.tomcat.util.net.jsse.JSSESupport.getPeerCertificateChain(boolean force) may be a good source of inspiration.
> Perhaps, client-certificate based authentication might be a candidate for a new jakarta commons component?
> It might not be long before Thunderbird starts offering this (https://bugzilla.mozilla.org/show_bug.cgi?id=290787)
> What will be very important that james can decide not just globally, but on a per-user basis whether client-certs shall be used for authentication or not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org