July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-151) Avoid Trigger collisions - Sprint-65

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-151?page=com.atlassian.jira.pl... ] Matt Mahoney updated HAWKULARQE-151: ------------------------------------ Description: Avoid Trigger collisions when MIQ is linked to multiple MIQ's Ref Sprint Review: https://www.youtube.com/watch?v=nXLLLv_QyP0&feature=em-subs_digest was: Avoid Trigger collisions when MIQ is linked to multiple MIQ's > Avoid Trigger collisions - Sprint-65 > ------------------------------------ > > Key: HAWKULARQE-151 > URL: https://issues.jboss.org/browse/HAWKULARQE-151 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Michael Foley > > Avoid Trigger collisions when MIQ is linked to multiple MIQ's > Ref Sprint Review: https://www.youtube.com/watch?v=nXLLLv_QyP0&feature=em-subs_digest -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-151) Avoid Trigger collisions - Sprint-65

by Matt Mahoney (JIRA)

Matt Mahoney created HAWKULARQE-151: --------------------------------------- Summary: Avoid Trigger collisions - Sprint-65 Key: HAWKULARQE-151 URL: https://issues.jboss.org/browse/HAWKULARQE-151 Project: Hawkular QE Issue Type: Task Reporter: Matt Mahoney Assignee: Michael Foley Avoid Trigger collisions when MIQ is linked to multiple MIQ's -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1312) Further Scoping and Caching Enhancements to the SpnegoAuthenticationMechanism

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1312: ------------------------------------- Summary: Further Scoping and Caching Enhancements to the SpnegoAuthenticationMechanism Key: ELY-1312 URL: https://issues.jboss.org/browse/ELY-1312 Project: WildFly Elytron Issue Type: Enhancement Components: HTTP Environment: # Reporter: Darran Lofthouse Fix For: 1.2.0.Beta1 Currently the SpnegoAuthenticationMechanism caches against the connection scope and uses the cached GssContext to recreate the identity. We should consider the following: - # Using the same cached identity mechanism as is used by FORM authentication. # Adding configuration to specify which scope to cache against. # Add an option to disable caching entirely, this would need to take into account cases where continuation is required as that would become unsupported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 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 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)

8 years, 3 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)

8 years, 3 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)

8 years, 3 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)

8 years, 3 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)

8 years, 3 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)

8 years, 3 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)

8 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2017