September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3098) Complete Undertow to JAAS Digest Integration

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3098?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3098: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha1) > Complete Undertow to JAAS Digest Integration > -------------------------------------------- > > Key: WFLY-3098 > URL: https://issues.jboss.org/browse/WFLY-3098 > Project: WildFly > Issue Type: Enhancement > Components: Security, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3221) flushOnSessionInvalidation attribute in jboss-web.xml does not flush user credentials

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3221?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3221: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha1) > flushOnSessionInvalidation attribute in jboss-web.xml does not flush user credentials > ------------------------------------------------------------------------------------- > > Key: WFLY-3221 > URL: https://issues.jboss.org/browse/WFLY-3221 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 8.0.0.Final > Reporter: Jorge Marmolejo > Assignee: Stuart Douglas > Priority: Critical > Fix For: 9.0.0.Beta1 > > > The attribute flushOnSessionInvalidation does not flush the user credentials when the session is invalidated or when it times out. If the password or roles change for the user, the only way to get the new changes is by restarting the server. > I tried removing "cache-type=default" from the standalone-full.xml and it works, but for every action made on the site, the login method in the authentication module is called. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3248) Clustering Extended testsuite is broken

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3248?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3248: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha1) > Clustering Extended testsuite is broken > --------------------------------------- > > Key: WFLY-3248 > URL: https://issues.jboss.org/browse/WFLY-3248 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 8.0.0.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Fix For: 9.0.0.Beta1 > > > What we did a while back, we made the sync-tcp the default configuration for running the clustering tests. However, we kept a extended testsuite with other combinations and other unimportant clustering tests. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3278) add-user for user admin / password admin says password must not match username but should say should

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3278?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3278: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha1) > add-user for user admin / password admin says password must not match username but should say should > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-3278 > URL: https://issues.jboss.org/browse/WFLY-3278 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Scripts > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3251) @WebContext overrides realm in web.xml

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3251?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3251: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha1) > @WebContext overrides realm in web.xml > -------------------------------------- > > Key: WFLY-3251 > URL: https://issues.jboss.org/browse/WFLY-3251 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 8.1.0.CR2 > Reporter: Juergen Zimmermann > Assignee: Alessio Soldano > Fix For: 9.0.0.Beta1 > > > In WEB-INF/web.xml I'm having this declaration (to be used for REST and SOAP): > {code} > <login-config> > <auth-method>BASIC</auth-method> > <realm-name>Shop</realm-name> > </login-config> > {code} > Furthermore, I'm having a SOAP-based web service: > {code} > @WebService(name = "KundeSOAP", > targetNamespace = "urn:shop:soap:kunde", > serviceName = "KundeSOAPService") > @SOAPBinding > @WebContext(authMethod = "BASIC", > transportGuarantee = "CONFIDENTIAL", > secureWSDLAccess = true) > @Stateless > @Interceptors(ConstraintViolationInterceptor.class) > @RolesAllowed({ "...", "..." }) > @SecurityDomain("...") > public class KundeSOAP {...} > {code} > But when the client invokes the server, then the realm name is "EJBWebServiceEndpointServlet Realm". -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3383) Enable user agent and address filters.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3383?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3383: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha1) > Enable user agent and address filters. > -------------------------------------- > > Key: WFLY-3383 > URL: https://issues.jboss.org/browse/WFLY-3383 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3348) DeploySingleServerGroupTestCase regularly fails on Windows

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3348?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3348: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha1) > DeploySingleServerGroupTestCase regularly fails on Windows > ---------------------------------------------------------- > > Key: WFLY-3348 > URL: https://issues.jboss.org/browse/WFLY-3348 > Project: WildFly > Issue Type: Bug > Components: CLI, Domain Management, Test Suite > Affects Versions: 8.1.0.CR2 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.2.0.CR1, 9.0.0.Beta1 > > > See http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=15206&tab=buil... for an example -- this fails repeatedly in the windows runs. > The @After method in the test asserts that the deployment file the test creates is successfully deleted. That may just be a bogus/unnecessary assertion, but rather than just removing it I thought it was better to check a bit first whether the CLI process is holding the file open. It shouldn't need to once upload of the deployment to the server is complete. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3434) Add xsd schemas on wildlfy.org

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3434?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3434: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha1) > Add xsd schemas on wildlfy.org > ------------------------------ > > Key: WFLY-3434 > URL: https://issues.jboss.org/browse/WFLY-3434 > Project: WildFly > Issue Type: Feature Request > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 9.0.0.Beta1 > > > we should have all wildfly releated schemas to wildfly.org/schema. > As part of this task, we need to update all docs to point to new URL. > have as much automated as possible process for uploading new schemas when new releases is done. > consolidate this over various (sub)projects that provide schemas that should be here. > What is not expected to be done is to host all old schemas that have nothing do do with WildFly on new location. > Example are most of pre AS7 jboss specific descriptors that WildFly no longer honors. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3443) JCA "tracking" should default to false for datasources

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3443?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3443: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha1) > JCA "tracking" should default to false for datasources > ------------------------------------------------------ > > Key: WFLY-3443 > URL: https://issues.jboss.org/browse/WFLY-3443 > Project: WildFly > Issue Type: Task > Components: JCA > Reporter: Scott Marlow > Assignee: Stefano Maestri > Fix For: 9.0.0.Beta1 > > > The [txtracking|http://www.ironjacamar.org/doc/roadto12/txtracking.html] feature is causing failures when IronJacamar closes the database connection in a Synchronization.afterCompletion() when a Hibernate Synchronization.afterCompletion() call already closed the connection. > See attached server.log for example of "IJ000315: Pool cts-derby-pool has 1 active handles" error. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3444) EjbTimerXmlPersister should check if timer.getNextExpiration() is null to avoid NPE

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3444?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3444: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha1) > EjbTimerXmlPersister should check if timer.getNextExpiration() is null to avoid NPE > ----------------------------------------------------------------------------------- > > Key: WFLY-3444 > URL: https://issues.jboss.org/browse/WFLY-3444 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Scott Marlow > Assignee: David Lloyd > Fix For: 9.0.0.Beta1 > > > Seeing a NPE in org.jboss.as.ejb3.timerservice.persistence.filestore.EjbTimerXmlPersister. that probably needs a null check: > {quote} > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.timerservice.persistence.filestore.EjbTimerXmlPersister.writeCalendarTimer(EjbTimerXmlPersister.java:136) > at org.jboss.as.ejb3.timerservice.persistence.filestore.EjbTimerXmlPersister.writeContent(EjbTimerXmlPersister.java:89) > at org.jboss.as.ejb3.timerservice.persistence.filestore.EjbTimerXmlPersister.writeContent(EjbTimerXmlPersister.java:43) > at org.jboss.staxmapper.XMLMapperImpl.doDeparse(XMLMapperImpl.java:88) > at org.jboss.staxmapper.XMLMapperImpl.deparseDocument(XMLMapperImpl.java:83) > at org.jboss.as.ejb3.timerservice.persistence.filestore.FileTimerPersistence.writeFile(FileTimerPersistence.java:440) > {quote} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

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 2014