river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Brouwer (JIRA)" <j...@apache.org>
Subject [jira] Work started: (RIVER-16) Mismatch key material and certificate stores utilized by X.500 discovery providers versus TLS endpoints
Date Wed, 28 Mar 2007 12:49:25 GMT

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

Work on RIVER-16 started by Mark Brouwer.

> Mismatch key material and certificate stores utilized by X.500 discovery providers versus
TLS endpoints
> -------------------------------------------------------------------------------------------------------
>
>                 Key: RIVER-16
>                 URL: https://issues.apache.org/jira/browse/RIVER-16
>             Project: River
>          Issue Type: Bug
>            Reporter: Mark Brouwer
>         Assigned To: Mark Brouwer
>            Priority: Critical
>
> Trust related questions for the TLS endpoints are answered through {{TrustManager}} instances
obtained through a configurable {{TrustManagerFactory}}, see [net.jini.jeri.sslSslEndpoint|http://java.sun.com/products/jini/2.1/doc/api/net/jini/jeri/ssl/package-frame.html].
This mechanism allows for an advanced implementation of a {{TrustManager}} that can answer
these questions based on context information associated with a service. E.g. Seven can have
completely different key material for each individual service running in a single JVM as the
trust related material is bound by a certain context.
> The X.500 discovery providers however can only have a single view on key material and
certificate stores through a few system properties as documented in the e.g. package [com.sun.jini.discovery.x500.sha1withdsa|http://java.sun.com/products/jini/2.1/doc/api/com/sun/jini/discovery/x500/sha1withdsa/package-frame.html],
preventing from having multiple views on key material depending on the context in which they
are handling discovery.
> Besides the system properties a trust provider mechanism is required that allows to specify
an implementation that can
> return a {{KeyStore}} and {{CertStore}} array depending on the context in which the discovery
operation must take place. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message