February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4360) Remove jboss-common-core.jar

by David Lloyd (JIRA)

David Lloyd created WFLY-4360: --------------------------------- Summary: Remove jboss-common-core.jar Key: WFLY-4360 URL: https://issues.jboss.org/browse/WFLY-4360 Project: WildFly Issue Type: Task Reporter: David Lloyd Completely remove the JAR and its module from the application server. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-159) Discovery of available algorithms for credential types

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-159?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-159: --------------------------------- It would be nice if the realm didn't actually have to know about the mechanism though; if we could just tell it what transformation applies and allow it to use some kind of pre-written code to do it then we can avoid requiring that knowledge. > Discovery of available algorithms for credential types > ------------------------------------------------------ > > Key: ELY-159 > URL: https://issues.jboss.org/browse/ELY-159 > Project: WildFly Elytron > Issue Type: Sub-task > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha1 > > > The overall purpose of the getCredentialSupport calls is so that we can discover information about the supported credentials as authentication mechanisms are offered - the algorithm for the digest is just as important as knowing the general type. > May just be a part of ELY-151 or may be something in addition. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-159) Discovery of available algorithms for credential types

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-159: ------------------------------------ Summary: Discovery of available algorithms for credential types Key: ELY-159 URL: https://issues.jboss.org/browse/ELY-159 Project: WildFly Elytron Issue Type: Sub-task Components: API / SPI Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha1 The overall purpose of the getCredentialSupport calls is so that we can discover information about the supported credentials as authentication mechanisms are offered - the algorithm for the digest is just as important as knowing the general type. May just be a part of ELY-151 or may be something in addition. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-720) KIE Server: enable automated testing on WebLogic 12

by Petr Široký (JIRA)

Petr Široký created DROOLS-720: ---------------------------------- Summary: KIE Server: enable automated testing on WebLogic 12 Key: DROOLS-720 URL: https://issues.jboss.org/browse/DROOLS-720 Project: Drools Issue Type: Task Affects Versions: 6.2.0.CR4 Reporter: Petr Široký Assignee: Petr Široký The `kie-server-tests` module does not have Cargo config for WebLogic. Cargo supports this container, so we should add the `wlc12x` profile to enable easy testing of the KIE Server also on WebLogic. http://cargo.codehaus.org/WebLogic+12.x -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-719) KIE Server: enable automated testing on WebSphere

by Petr Široký (JIRA)

Petr Široký created DROOLS-719: ---------------------------------- Summary: KIE Server: enable automated testing on WebSphere Key: DROOLS-719 URL: https://issues.jboss.org/browse/DROOLS-719 Project: Drools Issue Type: Task Affects Versions: 6.2.0.CR4 Reporter: Petr Široký Assignee: Petr Široký The `kie-server-tests` module does not have Cargo config for WebSphere. Cargo supports this container, so we should add the `was8x` profile to enable easy testing of the KIE Server also on WebSphere. I have an working PoC of this, so it should not be hard to port this into the sources. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-227) RejectedExecutionException when closing ModelControllerClient client

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-227?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-227: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1193926 > RejectedExecutionException when closing ModelControllerClient client > -------------------------------------------------------------------- > > Key: WFCORE-227 > URL: https://issues.jboss.org/browse/WFCORE-227 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Remoting > Affects Versions: 1.0.0.Alpha11 > Reporter: Alessio Soldano > Assignee: David Lloyd > Fix For: 1.0.0.Alpha15 > > > After wildfly-core 1.0.0.Alpha11 has been included in WFLY master, I'm seeing hundreds of the following exceptions in the logs when running the JBossWS-CXF testsuite: > {noformat} > Exception in thread "Remoting "management-client" task-4" java.util.concurrent.RejectedExecutionException: Task org.jboss.remoting3.remote.RemoteConnectionChannel$3@5651c0c2 rejected from org.xnio.XnioWorker$TaskPool@11462cd4[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 4] > at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048) > at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821) > at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1372) > at org.xnio.XnioWorker.execute(XnioWorker.java:741) > at org.jboss.remoting3.remote.RemoteConnectionChannel.receiveMessage(RemoteConnectionChannel.java:363) > at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:107) > at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:451) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > {noformat} > The exception is logged just after the org.jboss.as.webservices.deployer.RemoteDeployer calls the RemotingModelControllerClient#close method. > The issue seems to be related to some kind of race condition, as trying to reproduce it with an attached debugger is not possible. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-551) discovery-option and static-discovery resources miss add operation descriptions

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-551?page=com.atlassian.jira.plugin... ] Alexey Loubyansky closed WFCORE-551. ------------------------------------ Resolution: Cannot Reproduce Bug Appears to be fixed already. > discovery-option and static-discovery resources miss add operation descriptions > ------------------------------------------------------------------------------- > > Key: WFCORE-551 > URL: https://issues.jboss.org/browse/WFCORE-551 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha18 > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > Add operations for each of these resources require arguments but the descriptions are missing in the model. > To be able to invoke those operation from the CLI, the validation of operation requests has to be switched off. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-551) discovery-option and static-discovery resources miss add operation descriptions

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-551: ---------------------------------------- Summary: discovery-option and static-discovery resources miss add operation descriptions Key: WFCORE-551 URL: https://issues.jboss.org/browse/WFCORE-551 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 1.0.0.Alpha18 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Add operations for each of these resources require arguments but the descriptions are missing in the model. To be able to invoke those operation from the CLI, the validation of operation requests has to be switched off. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-875) SubjectCNMapping doesn't not manage correctly "Special Characters" like , (comma)

by Greg Autric (JIRA)

[ https://issues.jboss.org/browse/SECURITY-875?page=com.atlassian.jira.plug... ] Greg Autric updated SECURITY-875: --------------------------------- Attachment: picketbox.patch Patch to fix it > SubjectCNMapping doesn't not manage correctly "Special Characters" like , (comma) > ----------------------------------------------------------------------------------- > > Key: SECURITY-875 > URL: https://issues.jboss.org/browse/SECURITY-875 > Project: PicketBox > Issue Type: Bug > Components: JBossSX > Reporter: Greg Autric > Assignee: Stefan Guilhen > Attachments: CertificateTestCase.java, keystore.jks, picketbox.patch > > > If we have a certificate with a DN like this > "CN=Picketbox\, vault 2, OU=picketbox, O=JBoss, L=chicago, ST=il, C=us" (comma after Picketbox) > we get a Principal with ["picketbox] name instead of [Picketbox, vault 2] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-875) SubjectCNMapping doesn't not manage correctly "Special Characters" like , (comma)

by Greg Autric (JIRA)

[ https://issues.jboss.org/browse/SECURITY-875?page=com.atlassian.jira.plug... ] Greg Autric updated SECURITY-875: --------------------------------- Attachment: CertificateTestCase.java Test Case > SubjectCNMapping doesn't not manage correctly "Special Characters" like , (comma) > ----------------------------------------------------------------------------------- > > Key: SECURITY-875 > URL: https://issues.jboss.org/browse/SECURITY-875 > Project: PicketBox > Issue Type: Bug > Components: JBossSX > Reporter: Greg Autric > Assignee: Stefan Guilhen > Attachments: CertificateTestCase.java, keystore.jks > > > If we have a certificate with a DN like this > "CN=Picketbox\, vault 2, OU=picketbox, O=JBoss, L=chicago, ST=il, C=us" (comma after Picketbox) > we get a Principal with ["picketbox] name instead of [Picketbox, vault 2] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 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 February 2015