May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1097) FIPS CS, specific error message if keyAlias does not exist.

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/ELY-1097?page=com.atlassian.jira.plugin.s... ] Chao Wang reassigned ELY-1097: ------------------------------ Assignee: Chao Wang (was: Darran Lofthouse) > FIPS CS, specific error message if keyAlias does not exist. > ----------------------------------------------------------- > > Key: ELY-1097 > URL: https://issues.jboss.org/browse/ELY-1097 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Martin Choma > Assignee: Chao Wang > Fix For: 1.1.0.Beta39 > > > There is same error message if keyAlias does not exists and if exists but is of different type than SecretKey > _CredentialStoreException: ELY09512: External storage key under alias "key-alias" has to be a SecretKey_ > When alias does not exist error message should be more specific, e.g: > {{CredentialStoreException: ELY0XXXX: External storage key under alias "key-alias" does not exists}} > {code} > 09:48:44,127 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service org.wildfly.security.credential-store.fips-credential-store: org.jboss.msc.service.StartException in service org.wildfly.security.credential-store.fips-credential-store: WFLYELY00004: Unable to start the service. > at org.wildfly.extension.elytron.CredentialStoreService.start(CredentialStoreService.java:119) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.wildfly.security.credential.store.CredentialStoreException: ELY09512: External storage key under alias "key-alias" has to be a SecretKey > at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore$ExternalStorage.fetchStorageSecretKey(KeyStoreCredentialStore.java:1129) > at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore$ExternalStorage.init(KeyStoreCredentialStore.java:1105) > at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.setupExternalStorage(KeyStoreCredentialStore.java:885) > at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.load(KeyStoreCredentialStore.java:785) > at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.initialize(KeyStoreCredentialStore.java:183) > at org.wildfly.security.credential.store.CredentialStore.initialize(CredentialStore.java:119) > at org.wildfly.extension.elytron.CredentialStoreService.start(CredentialStoreService.java:117) > ... 5 more > 09:48:44,130 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("credential-store" => "fips-credential-store") > ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.credential-store.fips-credential-store" => "WFLYELY00004: Unable to start the service. > Caused by: org.wildfly.security.credential.store.CredentialStoreException: ELY09512: External storage key under alias \"key-alias\" has to be a SecretKey"}} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2141) RingBuffer should implement BlockingQueue

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2141?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2141: --------------------------- Fix Version/s: 4.1 (was: 4.x) > RingBuffer should implement BlockingQueue > ----------------------------------------- > > Key: JGRP-2141 > URL: https://issues.jboss.org/browse/JGRP-2141 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1 > > > Then we could use RingBuffer and queue in ThreadPoolExecutor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2031) GMS: replace ViewHandler.queue with BlockingQueue

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2031?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2031: --------------------------- Fix Version/s: 4.1 (was: 4.x) > GMS: replace ViewHandler.queue with BlockingQueue > ------------------------------------------------- > > Key: JGRP-2031 > URL: https://issues.jboss.org/browse/JGRP-2031 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1 > > > Replace {{GMS$ViewHandler.Queue}} with {{LinkedBlockingQueue}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2109) S3_PING: add support for instance metadata

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2109?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2109: --------------------------- Fix Version/s: 4.1 (was: 4.x) > S3_PING: add support for instance metadata > ------------------------------------------ > > Key: JGRP-2109 > URL: https://issues.jboss.org/browse/JGRP-2109 > Project: JGroups > Issue Type: Feature Request > Reporter: Kerem Kacel > Assignee: Bela Ban > Fix For: 4.1 > > > The AWS libraries used by S3_PING do not support authenticating into the AWS API via the EC2 instance profile (implicit credentials stored on the AWS EC2 instance). > The AWS SDK for Java supports instance profile. This eliminates the need for storing AWS access keys in config files. > Are there any plans to add official support for this in JGroups? > Resources: > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-roles.... > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html > Example third-party protocols: > https://github.com/tagbangers/jgroups-s3-client-ping > https://github.com/mcacker/jgroups-native-s3-ping -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2109) S3_PING: add support for instance metadata

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2109?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2109: -------------------------------- I recently rewrote natiev-s3-ping [1], can you take a look? I'd like to deprecate S3_PING as it started as a copy of AWS sample code, and doesn't use the official SDK. I suggest use AWS_PING or NATVE_S3_PING as replacement. [1] https://github.com/jgroups-extras/native-s3-ping > S3_PING: add support for instance metadata > ------------------------------------------ > > Key: JGRP-2109 > URL: https://issues.jboss.org/browse/JGRP-2109 > Project: JGroups > Issue Type: Feature Request > Reporter: Kerem Kacel > Assignee: Bela Ban > Fix For: 4.1 > > > The AWS libraries used by S3_PING do not support authenticating into the AWS API via the EC2 instance profile (implicit credentials stored on the AWS EC2 instance). > The AWS SDK for Java supports instance profile. This eliminates the need for storing AWS access keys in config files. > Are there any plans to add official support for this in JGroups? > Resources: > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-roles.... > http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html > Example third-party protocols: > https://github.com/tagbangers/jgroups-s3-client-ping > https://github.com/mcacker/jgroups-native-s3-ping -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1914) S3_PING doesn't work with S3 buckets created in Frankfurt region

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1914?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1914: --------------------------- Fix Version/s: 4.1 (was: 4.x) > S3_PING doesn't work with S3 buckets created in Frankfurt region > ----------------------------------------------------------------- > > Key: JGRP-1914 > URL: https://issues.jboss.org/browse/JGRP-1914 > Project: JGroups > Issue Type: Bug > Reporter: Gleb Leonov > Assignee: Bela Ban > Fix For: 4.1 > > Attachments: AWS4.png > > > I tried to use S3_PING with access and secret key pair. However, I got 400 (Bad Request) error. After some investigation, I found that modern S3 buckets created in Frankfurt needs amazon v4 authentication, which needs hmac-sha256. But now S3_PING supports only hmac-sha1, so I see no way to use S3_PING with buckets in Frankfurt region. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2091) Netty transport

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2091?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2091: --------------------------- Fix Version/s: 4.1 (was: 4.x) > Netty transport > --------------- > > Key: JGRP-2091 > URL: https://issues.jboss.org/browse/JGRP-2091 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.1 > > > Transport based on Netty. This should be useful to people already familiar with Netty. > Should be located in github.com/jgroups-extras as dependencies are introduced. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2091) Netty transport

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2091?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2091: --------------------------- Fix Version/s: 4.x (was: 4.1) > Netty transport > --------------- > > Key: JGRP-2091 > URL: https://issues.jboss.org/browse/JGRP-2091 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.x > > > Transport based on Netty. This should be useful to people already familiar with Netty. > Should be located in github.com/jgroups-extras as dependencies are introduced. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2108) TCP_NIO2: make default

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2108?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2108: --------------------------- Fix Version/s: 4.x (was: 4.1) > TCP_NIO2: make default > ---------------------- > > Key: JGRP-2108 > URL: https://issues.jboss.org/browse/JGRP-2108 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.x > > > This requires the following things: > * performance of {{TCP_NIO2}} must be better than {{TCP}} > * (possibly) use multiple selectors: each selector handles only a max number of connections; create more selectors when the number of connections per selector exceeds a certain value > * (possibly) get rid of the reader thread and let the above selector do the read (the write is already done by the selector thread) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2031) GMS: replace ViewHandler.queue with BlockingQueue

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2031?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2031: --------------------------- Fix Version/s: 4.x (was: 4.1) > GMS: replace ViewHandler.queue with BlockingQueue > ------------------------------------------------- > > Key: JGRP-2031 > URL: https://issues.jboss.org/browse/JGRP-2031 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.x > > > Replace {{GMS$ViewHandler.Queue}} with {{LinkedBlockingQueue}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2017