September 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5179) Some tests are unable to init arquillian protocol with security manager

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/WFLY-5179?page=com.atlassian.jira.plugin.... ] Ondrej Kotek edited comment on WFLY-5179 at 9/30/15 9:57 AM: ------------------------------------------------------------- Fixed test cases avoid using ManagementClient when running in non-RunAsClient mode. EjbLocalRefInjectionTestCase and EnvEntryInjectionTestCase were split -- no permissions needed. AuthenticationTestCase -and XTS TransactionalTestCase- have new permissions and comments. was (Author: okotek): Fixed test cases avoid using ManagementClient when running in non-RunAsClient mode. EjbLocalRefInjectionTestCase and EnvEntryInjectionTestCase were split -- no permissions needed. AuthenticationTestCase and XTS TransactionalTestCase have new permissions and comments. > Some tests are unable to init arquillian protocol with security manager > ----------------------------------------------------------------------- > > Key: WFLY-5179 > URL: https://issues.jboss.org/browse/WFLY-5179 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Marek Kopecký > Assignee: Ondrej Kotek > > *Description of problem:* > Some tests are unable to init arquillian protocol with security manager. > *Affected tests found so far:* > * org.jboss.as.test.integration.ee.injection.resource.ejblocalref.EjbLocalRefInjectionTestCase#testEjbLink > * org.jboss.as.test.integration.ee.injection.resource.ejblocalref.EjbLocalRefInjectionTestCase#testLookup > * org.jboss.as.test.integration.ee.injection.resource.enventry.EnvEntryInjectionTestCase#testEnvEntryInjectionIntoServlet > * org.jboss.as.test.integration.ejb.security.AuthenticationTestCase > * org.jboss.as.test.xts.annotation.client.TransactionalTestCase#testNoTransaction > * org.jboss.as.test.xts.annotation.client.TransactionalTestCase#testActiveTransaction > *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=EjbLocalRefInjectionTestCase > *Actual results:* > {noformat} > java.lang.RuntimeException: Could not init arquillian protocol > at org.xnio.Xnio.doGetInstance(Xnio.java:238) > at org.xnio.Xnio.getInstance(Xnio.java:193) > at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:112) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:122) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:147) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:122) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) > at org.jboss.as.arquillian.container.ManagementClient.init(ManagementClient.java:140) > at org.jboss.as.arquillian.container.ManagementClient.getWebUri(ManagementClient.java:177) > at org.jboss.as.test.integration.ee.injection.resource.ejblocalref.EjbLocalRefInjectionTestCase.performCall(EjbLocalRefInjectionTestCase.java:62) > at org.jboss.as.test.integration.ee.injection.resource.ejblocalref.EjbLocalRefInjectionTestCase.testEjbLink(EjbLocalRefInjectionTestCase.java:73) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1966) Specify logger name for LogRecord in JDKLogImpl

by George Zalizko (JIRA)

George Zalizko created JGRP-1966: ------------------------------------ Summary: Specify logger name for LogRecord in JDKLogImpl Key: JGRP-1966 URL: https://issues.jboss.org/browse/JGRP-1966 Project: JGroups Issue Type: Enhancement Affects Versions: 3.6.6 Reporter: George Zalizko Assignee: Bela Ban Priority: Minor I use Spring Boot with logback. For logging I have pattern: {code}%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} %C{30}:%L - %msg%n{code} And in console I see: {code} 16:19:32.062 [OOB-1,yphis-cluster-web,George-THINKPAD-35404] WARN unknown.jul.logger org.jgroups.logging.JDKLogImpl:49 - JGRP000010: packet from 192.168.50.123:45588 has different version (3.2.8) than ours (3.6.6); packet is discarded{code} This happens because LogRecord created in org.jgroups.logging.JDKLogImpl doesn't have loggerName and when org.slf4j.bridge.SLF4JBridgeHandler make org.slf4j.Logger from java.util.logging.LogRecord he sets logger name as org.slf4j.bridge.SLF4JBridgeHandler#UNKNOWN_LOGGER_NAME that's "unknown.jul.logger" Actually I don't know is it done specially or not, but I can't find any comments/solutions for that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-298) load-from/uri keystore xsd/parser mismatch

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-298?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-298: --------------------------------- Fix Version/s: 1.1.0.Alpha2 (was: 1.1.0.Alpha1) > load-from/uri keystore xsd/parser mismatch > ------------------------------------------ > > Key: ELY-298 > URL: https://issues.jboss.org/browse/ELY-298 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Kabir Khan > Assignee: Darran Lofthouse > Fix For: 1.1.0.Alpha2 > > > The xsd has > {code} > <xsd:complexType name="key-store-type"> > <xsd:sequence minOccurs="1" maxOccurs="1"> >  > <xsd:choice minOccurs="1" maxOccurs="1"> > <xsd:element name="file" type="name-type" minOccurs="1" maxOccurs="1"/> > <xsd:element name="load-from" type="uri-type" minOccurs="1" maxOccurs="1"/> > <xsd:element name="resource" type="name-type" minOccurs="1" maxOccurs="1"/> > {code} > The parser seems to look for 'uri' rather than 'load-from' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-290) Ensure a sensible default timeout on the LDAP connections

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-290?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-290: --------------------------------- Fix Version/s: 1.1.0.Alpha2 (was: 1.1.0.Alpha1) > Ensure a sensible default timeout on the LDAP connections > --------------------------------------------------------- > > Key: ELY-290 > URL: https://issues.jboss.org/browse/ELY-290 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Realms > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Alpha2 > > > By long enough I mean long enough to cope with network performance issues but short enough to prevent permanent hangs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-293) Add file based auth to http management interface

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-293?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-293: --------------------------------- Fix Version/s: 1.1.0.Alpha2 (was: 1.1.0.Alpha1) > Add file based auth to http management interface > ------------------------------------------------ > > Key: ELY-293 > URL: https://issues.jboss.org/browse/ELY-293 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Max Rydahl Andersen > Assignee: Darran Lofthouse > Fix For: 1.1.0.Alpha2 > > > usecase: allow clients using http api to use the file based auth so they do not have to rely on the binary protocol and remoting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-268) Review how mechanisms meet HttpAuthenticator

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-268?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-268: --------------------------------- Fix Version/s: 1.1.0.Alpha2 (was: 1.1.0.Alpha1) > Review how mechanisms meet HttpAuthenticator > -------------------------------------------- > > Key: ELY-268 > URL: https://issues.jboss.org/browse/ELY-268 > Project: WildFly Elytron > Issue Type: Sub-task > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Alpha2 > > > The current implementation is using a Supplier<List<HttpServerAuthenticationMechanism>> when get is called on this Supplier a ServerAuthenticationContext needs to be created, then all possible mechanisms need to be queried before the list of mechanisms is created. > The HTTP Authenticator is created per request. API may be fine but we may need an easier way to provide all the mechanisms. > Will look at that one later once hot deployment is also considered fully. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-270) Support separated columns for salt and cost when using the PasswordKeyMapper

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-270?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-270: --------------------------------- Fix Version/s: 1.1.0.Alpha2 (was: 1.1.0.Alpha1) > Support separated columns for salt and cost when using the PasswordKeyMapper > ---------------------------------------------------------------------------- > > Key: ELY-270 > URL: https://issues.jboss.org/browse/ELY-270 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Affects Versions: 1.0.0.Alpha3 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Alpha2 > > > Currently, the ```PasswordKeyMapper``` is only supporting BCRYPT passwords if they are stored using the Modular Crypt format. > Should also be possible to map BCRYPT passwords using separated columns for hash, salt and cost. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-279) Support CORS

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-279?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-279: --------------------------------- Fix Version/s: 1.1.0.Alpha2 (was: 1.1.0.Alpha1) > Support CORS > ------------ > > Key: ELY-279 > URL: https://issues.jboss.org/browse/ELY-279 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Alpha2 > > > This is something that can possibly be tied in around the HTTP authentication framework meaning that the control of this can live in the HTTP authentication policy within Elytron rather than at the front end. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-262) The equivalent of wrap and unwrap for HTTP authentication mechanisms

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-262?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-262: --------------------------------- Fix Version/s: 1.1.0.Alpha2 (was: 1.1.0.Alpha1) > The equivalent of wrap and unwrap for HTTP authentication mechanisms > -------------------------------------------------------------------- > > Key: ELY-262 > URL: https://issues.jboss.org/browse/ELY-262 > Project: WildFly Elytron > Issue Type: Sub-task > Components: HTTP > Reporter: Darran Lofthouse > Fix For: 1.1.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-208) Update SASL mechanism testing to also be domain backed.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-208?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-208: --------------------------------- Fix Version/s: 1.1.0.Alpha2 (was: 1.1.0.Alpha1) > Update SASL mechanism testing to also be domain backed. > ------------------------------------------------------- > > Key: ELY-208 > URL: https://issues.jboss.org/browse/ELY-208 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Darran Lofthouse > Assignee: Kabir Khan > Fix For: 1.1.0.Alpha2 > > > There may be a little bit more work required before this is possible but we need to ensure SASL mechanisms are also tested using a CallbackHandler they are likely to encounter which will really be the one from ServerAuthenticationContext. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 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 September 2015