July 2017 - jboss-jira - Jboss List Archives

[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 reopened JGRP-2141: ---------------------------- > 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.0.5 > > > Then we could use RingBuffer as queue in ThreadPoolExecutor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 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.0.5 (was: 4.1) > 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.0.5 > > > Then we could use RingBuffer as queue in ThreadPoolExecutor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 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 closed JGRP-2141. -------------------------- Resolution: Won't Fix See prev comment > 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.0.5 > > > Then we could use RingBuffer as queue in ThreadPoolExecutor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 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 closed JGRP-2141. -------------------------- Resolution: Won't Fix ThreadPoolExecutors in {{TP}} use {{SynchronousQueue}}, so this is not needed and as such closed as moot. > 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 as queue in ThreadPoolExecutor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 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: --------------------------- Description: Then we could use RingBuffer as queue in ThreadPoolExecutor (was: Then we could use RingBuffer and queue in ThreadPoolExecutor) > 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 as queue in ThreadPoolExecutor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1107) Wildfly Elytron Tool, Summary CLI command for adding new credential store contains duplicity for "create" and "location" attribute, "modification" attr is wrongly placed..

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/ELY-1107?page=com.atlassian.jira.plugin.s... ] Yeray Borges updated ELY-1107: ------------------------------ Fix Version/s: 1.1.0.Beta47 > Wildfly Elytron Tool, Summary CLI command for adding new credential store contains duplicity for "create" and "location" attribute, "modification" attr is wrongly placed.. > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-1107 > URL: https://issues.jboss.org/browse/ELY-1107 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Assignee: Yeray Borges > Fix For: 1.1.0.Beta47 > > > Summary CLI command for adding new credential store contains duplicity for "create" and "location" attribute, "modification" attr is wrongly placed.. > Create, location and modifiable attributes cannot be included in implementation-properties. "modifiable" attribute should be present in same way as "create" and "location" in its own attribute. > *How to reproduce* > {code} > java -jar wildfly-elytron-tool.jar credential-store --add secret_alias --password pass123 --create -x secret_password -l store.jceks --summary > {code} > {code} > /subsystem=elytron/credential-store=cs:add(relative-to=jboss.server.data.dir,location="store.jceks",create=true,implementation-properties={"keyStoreType"=>"JCEKS","create"=>"true","location"=>"store.jceks","modifiable"=>"true"},credential-reference={clear-text="pass123"}) > {code} > *It is expected some like this* > {code} > /subsystem=elytron/credential-store=cs:add(relative-to=jboss.server.data.dir,location="store.jceks",create=true, modifiable=true,implementation-properties={"keyStoreType"=>"JCEKS"},credential-reference={clear-text="pass123"}) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9152) CLIENT_CERT without users certificates database

by Jan Kalina (JIRA)

Jan Kalina created WFLY-9152: -------------------------------- Summary: CLIENT_CERT without users certificates database Key: WFLY-9152 URL: https://issues.jboss.org/browse/WFLY-9152 Project: WildFly Issue Type: Feature Request Components: Security Affects Versions: 11.0.0.Alpha1 Reporter: Jan Kalina Assignee: Jan Kalina Fix For: 12.0.0.Alpha1 CLIENT_CERT http-authentication-mechanism currently requires to provide security-realm, which will contain identity for given certificate and will verify X509Evidence for it. This does not provide replacement for legacy truststore auth, which allows to use only CA certificate to authenticate users by certificates signed by CA, without any database of them. Analysis document: https://developer.jboss.org/wiki/AnalysisDesign-CLIENTCERTWithoutUsersCer... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9151) CLIENT_CERT without users certificates database

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-9151?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-9151: ----------------------------- Fix Version/s: 12.0.0.Alpha1 > CLIENT_CERT without users certificates database > ----------------------------------------------- > > Key: WFLY-9151 > URL: https://issues.jboss.org/browse/WFLY-9151 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Jan Kalina > Assignee: Jan Kalina > Fix For: 12.0.0.Alpha1 > > > CLIENT_CERT http-authentication-mechanism currently requires to provide security-realm, which will contain identity for given certificate and will verify X509Evidence for it. This does not provide replacement for legacy truststore auth, which allows to use only CA certificate to authenticate users by certificates signed by CA, without any database of them. > Analysis document: > https://developer.jboss.org/wiki/AnalysisDesign-CLIENTCERTWithoutUsersCer... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9151) CLIENT_CERT without users certificates database

by Jan Kalina (JIRA)

Jan Kalina created WFLY-9151: -------------------------------- Summary: CLIENT_CERT without users certificates database Key: WFLY-9151 URL: https://issues.jboss.org/browse/WFLY-9151 Project: WildFly Issue Type: Feature Request Components: Security Affects Versions: 11.0.0.Alpha1 Reporter: Jan Kalina Assignee: Jan Kalina CLIENT_CERT http-authentication-mechanism currently requires to provide security-realm, which will contain identity for given certificate and will verify X509Evidence for it. This does not provide replacement for legacy truststore auth, which allows to use only CA certificate to authenticate users by certificates signed by CA, without any database of them. Analysis document: https://developer.jboss.org/wiki/AnalysisDesign-CLIENTCERTWithoutUsersCer... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3121) Elytron is registering resource /core-service=management/access=identity on a HostController

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3121?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3121: ------------------------------------- Fix Version/s: 3.0.0.CR1 (was: 3.0.0.Beta30) > Elytron is registering resource /core-service=management/access=identity on a HostController > -------------------------------------------------------------------------------------------- > > Key: WFCORE-3121 > URL: https://issues.jboss.org/browse/WFCORE-3121 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 3.0.0.CR1 > > > The Elytron integration added a resource registration for /core-service=management/access=identity on an HC. It should only be registered at /host=*/core-service=management/access=identity > The domain-wide /core-service=management resource MUST NOT HAVE CHILDREN REGISTERED other than access-authorization. It is not the place to configure HC-specific behavior. > I see use of this resource in enable-elytron.cli scripts used to configure the testsuite. At least in the one in WF full's testsuite/shared; I'm guessing elsewhere too. That must be changed. > If use of this domain-wide resource has ended up in any docs those must be corrected. > [~dlofthouse] FYI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2017