[JBoss JIRA] (ELY-296) Pass through Digest authentication against LDAP
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-296?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse moved WFLY-1217 to ELY-296:
--------------------------------------------
Project: WildFly Elytron (was: WildFly)
Key: ELY-296 (was: WFLY-1217)
Component/s: Realms
(was: Domain Management)
(was: Security)
Fix Version/s: (was: Awaiting Volunteers)
> Pass through Digest authentication against LDAP
> -----------------------------------------------
>
> Key: ELY-296
> URL: https://issues.jboss.org/browse/ELY-296
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Realms
> Reporter: Darran Lofthouse
> Labels: Common_Authentication
>
> It is possible for a client to authenticate against an LDAP server using Digest authentication.
> This task is to make use of this with both our SASL mechanism and HTTP authenticator to provide a pass through check.
> We need AS7-3691 first and then this needs to be implemented in a way that can consistently be used for both SASL and HTTP Digest.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5430) Rename the EJB3 subsystem to EJB
by David Lloyd (JIRA)
David Lloyd created WFLY-5430:
---------------------------------
Summary: Rename the EJB3 subsystem to EJB
Key: WFLY-5430
URL: https://issues.jboss.org/browse/WFLY-5430
Project: WildFly
Issue Type: Task
Components: EJB
Reporter: David Lloyd
Priority: Minor
I mean, really.
Retain compatibility with all previous configurations, operations, and schema which may use the name "ejb3".
Identify any public APIs under {{org.jboss.as.ejb3}} and ensure they are retained.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5167) IIOPNamingInContainer*TestCase can not connect to ORB with security manager
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-5167?page=com.atlassian.jira.plugin.... ]
Marek Kopecký reopened WFLY-5167:
---------------------------------
org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingInContainerTestCase#testStatefulIIOPNamingInvocation fails with this stacktrace:
{noformat}
org.omg.CORBA.UNKNOWN:
at com.sun.corba.se.spi.servicecontext.UEInfoServiceContext.<init>(UEInfoServiceContext.java:52)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at com.sun.corba.se.spi.servicecontext.ServiceContextData.makeServiceContext(ServiceContextData.java:132)
at com.sun.corba.se.spi.servicecontext.ServiceContexts.unmarshal(ServiceContexts.java:216)
at com.sun.corba.se.spi.servicecontext.ServiceContexts.get(ServiceContexts.java:378)
at com.sun.corba.se.spi.servicecontext.ServiceContexts.get(ServiceContexts.java:366)
at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(CorbaClientRequestDispatcherImpl.java:530)
at com.sun.corba.se.impl.protocol.SharedCDRClientRequestDispatcherImpl.marshalingComplete(SharedCDRClientRequestDispatcherImpl.java:222)
at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:148)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:475)
at org.jboss.as.ejb3.iiop.stub.DynamicIIOPStub.invoke(DynamicIIOPStub.java:127)
at interface org.jboss.as.test.integration.ejb.iiop.naming.IIOPStatefulNamingHome_Stub.create(Unknown Source)
at org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingInContainerTestCase.testStatefulIIOPNamingInvocation(IIOPNamingInContainerTestCase.java:60)
{noformat}
> IIOPNamingInContainer*TestCase can not connect to ORB with security manager
> ---------------------------------------------------------------------------
>
> Key: WFLY-5167
> URL: https://issues.jboss.org/browse/WFLY-5167
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.CR1
> Reporter: Marek Kopecký
> Assignee: Tomasz Adamski
> Fix For: 10.0.0.CR2
>
>
> *Description of problem:*
> Two tests can not connect to ORB with security manager. Tests run in "basic-integration-default-full.surefire" execution of basic profile.
> * org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingInContainerDDNameTestCase
> * org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingInContainerTestCase
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=IIOPNamingInContainerDDNameTestCase,IIOPNamingInContainerTestCase
> *Actual results:*
> {noformat}
> avax.naming.NamingException: WFLYIIOP0031: Cannot connect to ORB
> at com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2200)
> at com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2221)
> at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:223)
> at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:236)
> at com.sun.corba.se.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:119)
> at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:187)
> at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:137)
> at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:229)
> at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:130)
> at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
> at org.wildfly.iiop.openjdk.naming.jndi.CNCtx.setOrbAndRootContext(CNCtx.java:353)
> at org.wildfly.iiop.openjdk.naming.jndi.CNCtx.initUsingCorbanameUrl(CNCtx.java:335)
> at org.wildfly.iiop.openjdk.naming.jndi.CNCtx.initUsingUrl(CNCtx.java:268)
> at org.wildfly.iiop.openjdk.naming.jndi.CNCtx.initOrbAndRootContext(CNCtx.java:233)
> at org.wildfly.iiop.openjdk.naming.jndi.CNCtx.<init>(CNCtx.java:99)
> at org.wildfly.iiop.openjdk.naming.jndi.CNCtxFactory.getInitialContext(CNCtxFactory.java:53)
> at org.wildfly.iiop.openjdk.naming.jndi.WrapperInitialContext.lookup(WrapperInitialContext.java:72)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingInContainerDDNameTestCase.testIIOPNamingInvocationWithDDOverride(IIOPNamingInContainerDDNameTestCase.java:55)
> {noformat}
> *Expected results:*
> No errors on output
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5015) RunAs in servlet doesn't work
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-5015?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas reopened WFLY-5015:
--------------------------------
Reopen. See JBEAP-512 for details.
> RunAs in servlet doesn't work
> -----------------------------
>
> Key: WFLY-5015
> URL: https://issues.jboss.org/browse/WFLY-5015
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Security, Web (Undertow)
> Affects Versions: 10.0.0.Alpha6
> Reporter: Josef Cacek
> Assignee: Stuart Douglas
> Priority: Critical
> Fix For: 10.0.0.CR1
>
>
> RunAs for servlets doesn't work in Undertow.
> I have unprotected {{@RunAs}}-annotated servlet which calls protected EJB method. The call should succeed, but it throws {{javax.ejb.EJBAccessException}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5428) Xml files from wildfly don't end with "new line character"
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-5428?page=com.atlassian.jira.plugin.... ]
Marek Kopecký moved JBEAP-1181 to WFLY-5428:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-5428 (was: JBEAP-1181)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: Build System
(was: Build System)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 10.0.0.CR2
(was: 7.0.0.DR11 (Alpha))
> Xml files from wildfly don't end with "new line character"
> ----------------------------------------------------------
>
> Key: WFLY-5428
> URL: https://issues.jboss.org/browse/WFLY-5428
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.CR2
> Reporter: Marek Kopecký
> Assignee: Paul Gier
>
> *Description of problem:*
> * Some of xml files from *wildfly* don't end with "new line character".
> * Each xml file should end with "new line character", because of posix standard:
> ** http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#t...
> * List of affected files:
> ** ./docs/examples/configs/standalone-gossip-ha.xml
> ** ./docs/examples/configs/standalone-ec2-ha.xml
> ** ./docs/examples/configs/standalone-picketlink.xml
> ** ./docs/examples/configs/standalone-ec2-full-ha.xml
> ** ./docs/examples/configs/standalone-rts.xml
> ** ./docs/examples/configs/standalone-jts.xml
> ** ./docs/examples/configs/standalone-xts.xml
> ** ./docs/examples/configs/standalone-genericjms.xml
> ** ./docs/examples/configs/standalone-gossip-full-ha.xml
> ** ./standalone/configuration/standalone.xml
> ** ./standalone/configuration/standalone-ha.xml
> ** ./standalone/configuration/standalone-full.xml
> ** ./standalone/configuration/standalone-full-ha.xml
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # cd EAP_HOME
> # {noformat}
> for xml in `find -type f | grep xml$`; do
> if [ "`cat -E $xml | tail -n 1 |grep -o '.$'`" != "$" ] ; then
> echo $xml
> fi
> done
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-1021) Xml files from wildfly-core don't end with "new line character"
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1021?page=com.atlassian.jira.plugi... ]
Marek Kopecký moved JBEAP-1182 to WFCORE-1021:
----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1021 (was: JBEAP-1182)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: Server
(was: Build System)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.0.0.CR5
(was: 7.0.0.DR11 (Alpha))
> Xml files from wildfly-core don't end with "new line character"
> ---------------------------------------------------------------
>
> Key: WFCORE-1021
> URL: https://issues.jboss.org/browse/WFCORE-1021
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Affects Versions: 2.0.0.CR5
> Reporter: Marek Kopecký
> Assignee: Paul Gier
>
> *Description of problem:*
> * Some of xml files from *wildfly-core* don't end with "new line character".
> * Each xml file should end with "new line character", because of posix standard:
> ** http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#t...
> * List of affected files:
> ** ./modules/system/layers/base/org/wildfly/security/elytron/main/module.xml
> ** ./domain/configuration/host.xml
> ** ./domain/configuration/domain.xml
> ** ./domain/configuration/host-slave.xml
> ** ./domain/configuration/host-master.xml
> ** ./standalone/configuration/standalone.xml
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # cd EAP_HOME
> # {noformat}
> for xml in `find -type f | grep xml$`; do
> if [ "`cat -E $xml | tail -n 1 |grep -o '.$'`" != "$" ] ; then
> echo $xml
> fi
> done
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-829) Content repo gc task can delete content in mid-upload
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-829?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet closed WFCORE-829.
------------------------------------
Resolution: Rejected
The reopening is not correct as it is a bad usage of the API and NOT the same issue as the original one.
> Content repo gc task can delete content in mid-upload
> -----------------------------------------------------
>
> Key: WFCORE-829
> URL: https://issues.jboss.org/browse/WFCORE-829
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.0.Alpha10
> Reporter: Brian Stansberry
> Assignee: ehsavoie Hugonnet
>
> Description of problem:
> if upload of an application takes more than 5 minutes, it is removed from repository by clean-obsolete-content.
> - start the upload
> [Host Controller] 15:44:05,456 INFO [org.jboss.as.repository] (HttpManagementService-threads - 1) JBAS014900: Content added at location /opt/jboss-eap-6.4/domain-dc/data/content/90/828120fc51e4b5f5ededbb5981198b4be93e64/content
> - After 5 minutes, the content is removed:
> [Host Controller] 15:49:32,111 INFO [org.jboss.as.repository] (Host Controller Service Threads - 33) JBAS014903: Content /opt/jboss-eap-6.4/domain-dc/data/content/90/828120fc51e4b5f5ededbb5981198b4be93e64 is obsolete and will be removed
> [Host Controller] 15:49:32,113 INFO [org.jboss.as.repository] (Host Controller Service Threads - 33) JBAS014901: Content removed from location /opt/jboss-eap-6.4/domain-dc/data/content/90/828120fc51e4b5f5ededbb5981198b4be93e64/content
> The reference for the deployment is added to domain.xml only after the upload is finished.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (DROOLS-930) ClassCastException after segment split during incremental compilation
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-930?page=com.atlassian.jira.plugin... ]
Mario Fusco commented on DROOLS-930:
------------------------------------
This further commit is not strictly necessary for the fix but recommended to make sure that segment position is always set during segment creation https://github.com/droolsjbpm/drools/commit/efb85633b
> ClassCastException after segment split during incremental compilation
> ---------------------------------------------------------------------
>
> Key: DROOLS-930
> URL: https://issues.jboss.org/browse/DROOLS-930
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.4.x
>
>
> A segment split during an incremental compilation as in the following test case
> {code}
> @Test
> public void testSegmentSplitOnIncrementalCompilation() throws Exception {
> String drl =
> "import " + Person.class.getCanonicalName() + "\n" +
> "rule R1 when\n" +
> " $s : String()" +
> " Person( name == $s ) \n" +
> "then\n" +
> " System.out.println(\"Triggered: R1\");\n" +
> "end\n" +
> "rule R2 when\n" +
> " $s : String()" +
> " Person( name == $s ) \n" +
> "then\n" +
> " System.out.println(\"Triggered: R2\");\n" +
> "end\n" +
> "rule R3 when\n" +
> " $s : String()" +
> " Person( name != $s ) \n" +
> "then\n" +
> " System.out.println(\"Triggered: R3\");\n" +
> "end\n";
> KieServices ks = KieServices.Factory.get();
> ReleaseId releaseId1 = ks.newReleaseId("org.kie", "test-upgrade", "1.1.1");
> KieModule km = createAndDeployJar(ks, releaseId1);
> KieContainer kc = ks.newKieContainer(km.getReleaseId());
> KieSession ksession = kc.newKieSession();
> kc.updateToVersion(releaseId1);
> ksession.insert(new Person("John", 26));
> ksession.insert( "John" );
> ksession.fireAllRules();
> ReleaseId releaseId2 = ks.newReleaseId("org.kie", "test-upgrade", "1.1.2");
> km = createAndDeployJar(ks, releaseId2, drl);
> kc.updateToVersion(releaseId2);
> ksession.fireAllRules();
> }
> {code}
> may cause the following ClassCastException during the subsequent network evaluation
> {code}
> java.lang.ClassCastException: org.drools.core.reteoo.RuleTerminalNode cannot be cast to org.drools.core.reteoo.LeftInputAdapterNode
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:99)
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:73)
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:978)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1292)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1294)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1260)
> at org.drools.compiler.integrationtests.IncrementalCompilationTest.testSegmentSplit(IncrementalCompilationTest.java:2001)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5427) If used journal object store (AMQ Artemis journal) directory is named HornetqObjectStore
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created WFLY-5427:
--------------------------------------
Summary: If used journal object store (AMQ Artemis journal) directory is named HornetqObjectStore
Key: WFLY-5427
URL: https://issues.jboss.org/browse/WFLY-5427
Project: WildFly
Issue Type: Bug
Components: Transactions
Affects Versions: 10.0.0.CR2
Reporter: Ondřej Chaloupka
Assignee: Amos Feng
Priority: Minor
Directory of transaction object store is named {{standalone/data/tx-object-store/HornetqObjectStore}}. The WFLY 10 does not use HornetQ object store but it uses ActiveMQ Artemis object store. That's same for the Transaction subsystem.
The journal dirctory should be renamed to {{JournalObjectStore}} or something similar.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months