and TrustManager algorithm not supported
> ---
>
> Key: ZOOKEEPER-2429
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2429
> Project: ZooKeeper
> Issue Type: Bug
>
and TrustManager algorithm not supported
> ---
>
> Key: ZOOKEEPER-2429
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2429
> Project: ZooKeeper
> Issue Type: Bug
eady exists for the same problem then there is no
meaning in reinventing the wheel.
I had gone through the classes as you mentioned in the above comment and will
take the same approach to fix it.
Thanks for pointing it out.
I will keep you posted once i test it.
> IbmX509 KeyManager and Trust
> IbmX509 KeyManager and TrustManager algorithm not supported
> ---
>
> Key: ZOOKEEPER-2429
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2429
> Project: ZooKeeper
>
the original implementation from Hadoop, so this
makes sense to me (what Chris said).
> IbmX509 KeyManager and TrustManager algorithm not supported
> ---
>
> Key: ZOOKEEPER-2429
> URL: https:
9 KeyManager and TrustManager algorithm not supported
> ---
>
> Key: ZOOKEEPER-2429
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2429
> Project: ZooKeeper
> Issue T
Additional user-facing configuration for this might not be necessary, and
it might push more operational complexity onto administrators. FWIW,
there is a bit of code in Hadoop that takes the approach of runtime
detection of the IBM JRE, and then automatically toggles between the two
algorithms. S
word
2 new properties can also be defined in the server startup script.
-Dzookeeper.ssl.keyManager.algorithm
-Dzookeeper.ssl.trustManager.algorithm
If the properties are missing then it will fallback to the default algorithm
supported by underlying jre.
> IbmX509 KeyManager and TrustManager al
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2429:
Assignee: Saurabh jain
> IbmX509 KeyManager and TrustManager algorithm not suppor
Yeah , I created my jira user account recently more specifically on 13th
may I think.
Nevermind we can track with this new jira (2429).
Please assign this jira to me.
On Tue, May 17, 2016 at 12:06 PM, Patrick Hunt wrote:
> The Apache infra team has been dealing with a massive JIRA spam attack
The Apache infra team has been dealing with a massive JIRA spam attack over
the past few days (not the first time). I'm not sure but it could be that
some of the counter-measures and/or cleanup implemented by the infra team
to address the spam may have caused your jira to go missing. Did you create
I had created a new jira for this -
https://issues.apache.org/jira/browse/ZOOKEEPER-2429.
I will go through the process on how to contribute and will submit the
patch as per Patrick's recommendation.
On Tue, May 17, 2016 at 10:14 AM, Patrick Hunt wrote:
> There was a discussion about that rece
-
Makes sense to me. However I'd recommend that you make it configurable.
Make the default getDefaultAlgo, but allow it to be overridden by the user
via configuration at the ZK level. Print a debug level message with the
value used for debuggability.)
> IbmX509 KeyManager and TrustManager algor
yManager and TrustManager algorithm not supported
> ---
>
> Key: ZOOKEEPER-2429
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2429
> Project: ZooKeeper
> Issue T
Saurabh Jain created ZOOKEEPER-2429:
---
Summary: IbmX509 KeyManager and TrustManager algorithm not
supported
Key: ZOOKEEPER-2429
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2429
Project
There was a discussion about that recently, looks like an INFRA issue, see
http://markmail.org/message/r2nbgezn7cpldupz
Try re-creating the jira.
Patrick
On Tue, May 17, 2016 at 7:02 AM, saurabh jain wrote:
> Hello Patrick,
>
> Yeah , that would be flexible to make it configurable.
> Can I op
Hello Patrick,
Yeah , that would be flexible to make it configurable.
Can I open a Jira for this ?
Earlier I created a jira (ZOOKEEPER-2428) for this not sure why it was
removed.
Thanks,
Saurabh
On Mon, May 16, 2016 at 6:20 PM, Patrick Hunt wrote:
> Makes sense to me. However I'd recommend th
Makes sense to me. However I'd recommend that you make it configurable.
Make the default getDefaultAlgo, but allow it to be overridden by the user
via configuration at the ZK level. Print a debug level message with the
value used for debuggability.
Patrick
On Mon, May 16, 2016 at 7:24 AM, saurabh
Hello All ,
When connecting from a zookeeper client running in IBM WebSphere
Application Server version 8.5.5, with SSL configured in ZooKeeper, the
below mentioned exception is observed.
org.jboss.netty.channel.ChannelPipelineException: Failed to initialize a
pipeline.
at org.jboss.netty.b
atch for this. Please let me know if the proposed
solution in the description is inline with the zookeeper framework or any other
inputs are most welcome.
> IbmX509 KeyManager and TrustManager algorithm not supported
> ---
>
>
;);
can we have ?
KeyManagerFactory kmf =
KeyManagerFactory.getInstance(KeyManagerFactory.getDefaultAlgorithm());
TrustManagerFactory tmf =
TrustManagerFactory.getInstance(TrustManagerFactory.getDefaultAlgorithm());
> IbmX509 KeyManag
Saurabh Jain created ZOOKEEPER-2428:
---
Summary: IbmX509 KeyManager and TrustManager algorithm not
supported
Key: ZOOKEEPER-2428
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2428
Project
22 matches
Mail list logo
